Actions
Bug #5707
closedxsl:output with json-node-output-method="adaptive" does not work
Start date:
2022-10-03
Due date:
% Done:
100%
Estimated time:
Legacy ID:
Applies to branch:
10, 11, trunk
Fix Committed on Branch:
10, 11, trunk
Description
It seems that if you set json-node-output-method="adaptive" on an xsl:output element, Saxon displays an error:
Error in xsl:output/@json-node-output-method on line 3 column 67 of jsonAdaptiveoutput.xsl:
XTSE0020 Invalid value (adaptive) for serialization method: must be
xml|html|xhtml|text|json|adaptive, or a QName in 'Q{uri}local' form
<?xml version="1.0" encoding="UTF-8"?>
<xsl:stylesheet xmlns:xsl="http://www.w3.org/1999/XSL/Transform" version="3.0">
<xsl:output method="json" json-node-output-method="adaptive"/>
</xsl:stylesheet>
I tested with Saxon 10.8, 11.2, and 11.4
Updated by Michael Kay about 2 years ago
- Subject changed from xslLoutout with json-node-output-method="adaptive" does not work to xsl:output with json-node-output-method="adaptive" does not work
Updated by Michael Kay about 2 years ago
Well, it's obviously a bad error message.
The table at the start of section 3 of the serialization spec says the value must be:
An expanded QName with a non-null namespace URI, or with a null namespace URI and a local name equal to one of xml, xhtml, html or text.
So we'll keep the restriction and improve the error message.
Updated by Michael Kay about 2 years ago
- Category set to Diagnostics
- Status changed from New to Resolved
- Assignee set to Michael Kay
- Applies to branch 10, 11, trunk added
- Fix Committed on Branch 10, 11, trunk added
- Platforms .NET, Java added
Updated by Community Admin almost 2 years ago
- % Done changed from 0 to 100
- Fixed in Maintenance Release 12.0 added
Bug issue fix applied in the Saxon 12.0 Major Release. Leaving this bug marked as Resolved until fix applied
Updated by O'Neil Delpratt almost 2 years ago
- Fixed in Maintenance Release 11.5 added
Bug fix applied in the Saxon 11.5 maintenance release.
Updated by O'Neil Delpratt almost 2 years ago
- Status changed from Resolved to Closed
- Fixed in Maintenance Release 10.9 added
Bug fix applied in the Saxon 10.9 maintenance release.
Please register to edit this issue
Actions