Bug #3865
closedIssues running 9.9 SEFs with Saxon-JS 1.1.0
100%
Description
There are some differences in SEFs generated by 9.9 compared to 9.8, which the current Saxon-JS release 1.1.0 cannot handle. Use this bug to keep track of problems with running SEFs generated by Saxon-EE 9.9 (with -export:JS) with Saxon-JS 1.1.0.
Related issues
Updated by Debbie Lockett over 6 years ago
- Running XsltTestSuiteDriverJS in 9.9, a number of XSLT 3.0 tests fail with "Undeclared prefix", e.g. -s:attribute -t:attribute-0001 This is due to the fact that with 9.9, namespace declarations are no longer exported inside SEFs.
e.g. 9.8 SEF: <att xmlns:p="http://ns.p.com/" name="p:local" nsuri="http://ns.p.com/" flags="l">
9.9 SEF: <att name="p:local" nsuri="http://ns.p.com/" flags="l">
When processing the "att" expression, Saxon-JS 1.1.0 ignores att/@nsuri
, and just attempts to use namespace declarations to resolve lexical QNames.
It was a design decision to remove the namespace declarations inside 9.9 SEFs; so this requires a fix in Saxon-JS. When att/@nsuri
is available, it should be used (note that 9.7 SEFs do not include att/@nsuri
, so we still need to handle this case).
Updated by Debbie Lockett over 6 years ago
.2. A couple of XSLT 3.0 tests fail with "Undeclared prefix: err" e.g. -s:maps -t:maps-009
In 9.9, "err" has been added to the list of commonly-used conventional prefixes; see NamespaceConstant.getUriForConventionalPrefix. So when outputting the in-scope namespaces in the 9.9 SEF, we now get err=~
.
In Saxon-JS 1.x, KNOWN_URI (in Expr.js) should be updated to realign with this list.
Updated by Debbie Lockett over 6 years ago
- Status changed from New to In Progress
Patches committed in Expr.js on Saxon-JS 1.x branch, to fix issues 1 and 2.
Updated by Debbie Lockett about 6 years ago
- Related to Bug #3813: Should add err=http://www.w3.org/2005/xqt-errors to the list of conventional namespace bindings added
Updated by Debbie Lockett about 6 years ago
- Project changed from 4 to SaxonJS
- Applies to JS Branch 1.0 added
Moving this bug into the Saxon-JS project, now that 9.9 is released. (Note that the code patches have been for Saxon-JS code.)
Updated by Debbie Lockett about 6 years ago
- Status changed from In Progress to Resolved
- Fix Committed on JS Branch 1.0 added
Marking as resolved, no further issues have arisen.
Updated by Debbie Lockett about 6 years ago
- Status changed from Resolved to Closed
- % Done changed from 0 to 100
- Fixed in JS Release set to Saxon-JS 1.2.0
Bug fix applied in the Saxon-JS 1.2.0 maintenance release.
Please register to edit this issue
Also available in: Atom PDF Tracking page