Project

Profile

Help

Bug #4624

closed

Matching with namespaces in SaxonJS / NodeJS

Added by Wendell Piez almost 4 years ago. Updated about 3 years ago.

Status:
Closed
Priority:
Normal
Assignee:
Category:
XSLT Conformance
Sprint/Milestone:
-
Start date:
2020-06-29
Due date:
% Done:

100%

Estimated time:
Applies to JS Branch:
2
Fix Committed on JS Branch:
2
Fixed in JS Release:
SEF Generated with:
Platforms:
Company:
-
Contact person:
-
Additional contact persons:
-

Description

Using SaxonJS and invoking from the node-js CL, I am finding that namespaces are not lining up as expected.

An XSLT is attached. It can be run on itself. It shows two key declarations, both of which should work, but only one does. The one that does not work is relying on an xpath-default-namespace setting for matching. The one that works uses an explicit namespace prefix (matching an element with an unprefixed name in the input document). Plain template matches work fine with the xpath-default-namespace setting.

Thanks! Wendell


Files

ns-bug1.xsl (1.14 KB) ns-bug1.xsl Wendell Piez, 2020-06-29 18:35

Related issues

Has duplicate SaxonJS - Bug #4630: Elements not matched when using `match="foo[. is key('some-key', value)[1]]"` if elements are in a namespace and xpath-default-namespace is usedDuplicate2020-07-03

Actions

Please register to edit this issue

Also available in: Atom PDF Tracking page