Page 1 of 1

Using Saxon 9.7 and XSLT 3.0 and output method="adpative"

Posted: Wed May 11, 2016 1:09 pm
by Martin Honnen
Using oXygen 18 and an XSLT 3.0 transformation with Saxon 9.7 EE added as an external XSLT engine I don't get the right output when using the new output method adaptive and outputting values like an array, for instance the minimal XSLT stylesheet

Code: Select all

<?xml version="1.0" encoding="UTF-8"?>
<xsl:stylesheet xmlns:xsl="http://www.w3.org/1999/XSL/Transform"
xmlns:xs="http://www.w3.org/2001/XMLSchema"
xmlns:math="http://www.w3.org/2005/xpath-functions/math"
xmlns:array="http://www.w3.org/2005/xpath-functions/array"
xmlns:mf="http://example.com/mf"
exclude-result-prefixes="xs math array mf"
version="3.0">

<xsl:output method="adaptive"/>

<xsl:template name="main">
<xsl:sequence select="[1, 2, 3]"/>
</xsl:template>

</xsl:stylesheet>
inside of oXygen outputs

Code: Select all

1 2 3
in the result pane while Saxon run from the command line outputs the correct array syntax

Code: Select all

[1,2,3]

Re: Using Saxon 9.7 and XSLT 3.0 and output method="adpative"

Posted: Thu May 12, 2016 10:07 am
by alex_jitianu
Hi Martin,

Thank you for reporting this Saxon 9.7 related issue. I've investigated a bit and it looks like the "adaptive" method is explicitly handled inside the command line entry point: net.sf.saxon.Transform. We are using Saxon through its Java API for XML Processing (JAXP) implementations and it looks like these implementations don't handle the "adaptive" method.

I will contact Saxonica and ask for their advice on how to solve this issue. If we are lucky we'll be able to perform a fix on our side. If not, then we'll need a new Saxon 9.7 build. I'll keep you posted!

Best regards,
Alex

Re: Using Saxon 9.7 and XSLT 3.0 and output method="adpative"

Posted: Mon Oct 02, 2017 3:38 pm
by Radu
Hi,

The Oxygen 19.1 release should also fix this issue.

Regards,
Radu