Bug #5008
closedSaxonJS: Import XSLT2 from XSLT2 error
100%
Description
With SaxonJS 2.2.0, given XSL v1, that imports v2, the following error is received:
Transformation failure: Error SESU0013 Serializer does not support the requested XML version: 2.0
This same set of files may be processed without error using Saxon-HE. Note: this error was encountered with the Schematron pipeline implemented here: https://github.com/18F/fedramp-automation/blob/master/resources/validations/bin/validate_with_schematron.sh
For a minimal reproduction, see here: https://github.com/danielnaab/xslt3-import-bug-repro
The details in the repro are below, for reference:
npx xslt3 -s:./source.sch -xsl:transform.xsl -o:./output.xsl
source.sch:
<?xml version="1.0" encoding="UTF-8"?>
<sch:schema xmlns:sch="http://purl.oclc.org/dsdl/schematron" queryBinding="xslt2">
</sch:schema>
XSL:
transform.xsl:
<?xml version="1.0"?>
<xsl:stylesheet version="1.0" xmlns:xsl="http://www.w3.org/1999/XSL/Transform">
<xsl:import href="import.xsl" />
</xsl:stylesheet>
import.xsl:
<?xml version="1.0"?>
<xsl:stylesheet xmlns:xsl="http://www.w3.org/1999/XSL/Transform" version="2.0">
<xsl:output />
</xsl:stylesheet>
Updated by Debbie Lockett over 3 years ago
- Category set to XX compiler
- Status changed from New to In Progress
- Applies to JS Branch 2 added
Thanks for reporting the bug, and supplying the repro. I have reproduced the problem, and can confirm that this is a XX compiler issue.
Test (J-08) added to the xslt3_test.js mocha test set.
Updated by Debbie Lockett over 3 years ago
- Status changed from In Progress to Resolved
- Fix Committed on JS Branch 2 added
Fix committed in XX compiler. In static.xsl line 996, add xsl:output
to the list of excluded elements when $stylesheet-properties
is copied to a child of xsl:stylesheet
.
Updated by Alexander Stein over 3 years ago , visible to Alexander Stein - QN-C (alexander.stein@gsa.gov) from Alexander Stein - QN-C
- Company set to Alexander Stein - QN-C
- Contact person set to Alexander Stein - QN-C
Hello,
Can you please give a status update and indicate:
- When will this be part of a release of SaxonJS to npmjs?
- Do you offer alpha or beta releases of fixes in the SaxonJS library?
We would like to help confirm the bug is fixed before having to re-open or
create another issue if that is avoidable.
Thanks in advance for your help and cooperation.
Updated by Debbie Lockett over 3 years ago
Hi Alexander, answering the question of when the next release will be out is always a hard one. But understanding the importance of this bug fix to you certainly influences our plans. Clearly it would be useful for us to put out a new bug fixing maintenance release as soon as possible. As long as nothing unexpected crops up, hopefully we can get a maintenance release out in August.
Updated by Debbie Lockett over 3 years ago
- % Done changed from 0 to 100
- Fixed in JS Release set to Saxon-JS 2.3
Bug fix applied in the Saxon-JS 2.3 maintenance release.
Updated by Debbie Lockett over 3 years ago
- Status changed from Resolved to Closed
Please register to edit this issue
Also available in: Atom PDF Tracking page