Bug #6054: NamedNodeMap.getNamedItem throw UnsupportedOperationException - Saxon - Saxonica Developer Community

Actions

Send by e-mail Copy link

Bug #6054

closed

NamedNodeMap.getNamedItem throw UnsupportedOperationException

Added by Khalil Rahmouni 11 months ago. Updated 8 months ago.

Status:

Closed

Priority:

Normal

Assignee:

Michael Kay

Category:

DOM Interface

Sprint/Milestone:

Start date:

2023-05-30

Due date:

% Done:

100%

Estimated time:

Legacy ID:

Applies to branch:

11, 12, trunk

Fix Committed on Branch:

11, 12, trunk

Fixed in Maintenance Release:

12.3, 11.6

Platforms:

Java

Description

i use the following Code to extract the value of an attribute, it works fine with version 9.9 but with version 11.5 it throw an exception : UnsupportedOperationException: NodePredicate doesn't support this method.

EnterpriseConfiguration config = new EnterpriseConfiguration();

        NodeInfo rootNode = config.buildDocumentTree(new StreamSource(resourceAsStream)).getRootNode();
        Document document = (Document) DocumentOverNodeInfo.wrap(rootNode);

        Element documentElement1 = document.getDocumentElement();
        NamedNodeMap attributes1 = documentElement1.getAttributes();
        Node namedItem1 = attributes1.getNamedItem("xsi:schemaLocation");

Files

valid_baseProduct.xml (1.38 KB) valid_baseProduct.xml

Khalil Rahmouni, 2023-05-30 15:40

Actions

Copy link

Updated by Michael Kay 11 months ago

Category set to DOM Interface
Status changed from New to In Progress
Assignee set to Michael Kay
Priority changed from Low to Normal

Thanks for reporting it. Reproduced as JUnit test DOMTest.testBug6054.

Actions

Copy link

Updated by Michael Kay 11 months ago

Now fixed. I have to confess the DOM-over-Saxon node wrapper (NodeOverNodeInfo) doesn't have very good test coverage. It was changed a little to adapt to interface changes introduced for C# transpilation, and it looks like this particular path wasn't covered by regression tests. This is one of the few places we try to find an attribute by its lexical QName rather than its namespace URI plus local name, a consequence of DOM not being fully namespace-aware.

Actions

Copy link

Updated by Michael Kay 11 months ago

Status changed from In Progress to Resolved
Applies to branch 12, trunk added
Fix Committed on Branch 11, 12, trunk added

Actions

Copy link

Updated by Khalil Rahmouni 11 months ago

i downloaded saxon 11.5 ee again, but i still get the same error , does the download jar contains the fix already?

Actions

Copy link

Updated by Michael Kay 11 months ago

No, sorry, "resolved" means that we have applied and tested a fix. When we issue a maintenance release containing the fix, we'll update the status of the issue to indicate this. (If you're really keen you can build the Saxon-HE product yourself from the source code repository, but it's not something for the faint-hearted).

Actions

Copy link