Bug #2163
closed
saxon:next-in-chain is not working in Saxon 9.6
Category:
Saxon extensions
Fix Committed on Branch:
9.6
Fixed in Maintenance Release:
Description
Added JUnit test JAXPTests/SerializerTests/tetNextInChain.
- Status changed from New to Resolved
Patched on the 9.6 and 9.7 branches, and unit tested. The fix is in two parts: (a) for an unnamed xsl:output element, the work is done in the s9api XsltTransformer class; when setting a Destination object, if saxon:next-in-chain was specified in the stylesheet, then the requested transformation is interposed before the specified Destination. (b) for xsl:result-document, both with and without the "href", with a named xsl:output declaration, the work is done in SerializerFactory and SerializerFactoryPE.
Note that saxon:next-in-chain is not supported when the Xslt30Transformer class is used, as it gets very messy, and there are much simpler ways now of setting up a chain of transformations. A warning is issued saying the attribute is ignored.
- Status changed from Resolved to Closed
- % Done changed from 0 to 100
- Fixed in version set to 9.6.0.2
Bug fix applied to the maintenance release Saxon 9.6.0.2
- Sprint/Milestone set to 9.6.0.2
- Applies to branch 9.6 added
- Fix Committed on Branch 9.6 added
- Fixed in Maintenance Release 9.6.0.2 added
Please register to edit this issue
Also available in: Atom
PDF
.