Project

Profile

Help

Bug #2163

saxon:next-in-chain is not working in Saxon 9.6

Added by Michael Kay almost 5 years ago. Updated almost 4 years ago.

Status:
Closed
Priority:
Normal
Assignee:
Category:
Saxon extensions
Sprint/Milestone:
Start date:
2014-10-06
Due date:
% Done:

100%

Legacy ID:
Applies to branch:
9.6
Fix Committed on Branch:
9.6
Fixed in Maintenance Release:

Description

Added JUnit test JAXPTests/SerializerTests/tetNextInChain.

History

#1 Updated by Michael Kay almost 5 years ago

  • 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.

#2 Updated by O'Neil Delpratt almost 5 years ago

  • 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

#3 Updated by O'Neil Delpratt almost 4 years ago

  • 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