Actions
Bug #5602
closed![Author: Octavian Nadolu](https://www.gravatar.com/avatar/eee430f219c32639a71b4d2e6e5c1e85?rating=PG&size=50&default=https%3A%2F%2Fassets.plan.io%2Fimages%2Fdefault_avatar.png)
![Assignee: Michael Kay](https://www.gravatar.com/avatar/db6526d63053f09b62e52c2da8b2230a?rating=PG&size=22&default=https%3A%2F%2Fassets.plan.io%2Fimages%2Fdefault_avatar.png)
Namespace prefix not taken from context
Start date:
2022-07-13
Due date:
% Done:
100%
Estimated time:
Legacy ID:
Applies to branch:
11, trunk
Fix Committed on Branch:
11, trunk
Fixed in Maintenance Release:
Platforms:
Description
It I transform the attached test.xml with test.xsl, using Saxon HE 11.3, the resulting document is something like this:
<test xmlns:ns0="http://www.oxygenxml.com/schematron/validation" ns0:elementURI="base-uri()"/>
If I perform the same transformation with Saxon HE 10.6, the resulting document is something like this:
<test xmlns:oxy="http://www.oxygenxml.com/schematron/validation" oxy:elementURI="base-uri()"/>
It seems that in Saxon 11.3 the namespace declaration from the XSL document is not used anymore for the result.
Files
Updated by Michael Kay about 2 years ago
- Category set to Internals
- Status changed from New to Resolved
- Assignee set to Michael Kay
- Applies to branch 11, trunk added
- Fix Committed on Branch 11, trunk added
This is indeed a bug, caused by using equals()
to compare a String and a UnicodeString in XSLAttribute line 234.
Note, also, the current code which uses the namespace axis to search the in-scope namespaces could be streamlined by using the inScopeNamespaces() NamespaceMap.
Updated by Debbie Lockett almost 2 years ago
- Status changed from Resolved to Closed
- % Done changed from 0 to 100
- Fixed in Maintenance Release 11.4 added
Bug fix applied in the Saxon 11.4 maintenance release.
Please register to edit this issue
Actions