Using Saxon 9.7 and XSLT 3.0 and output method="adpative"
Having trouble installing Oxygen? Got a bug to report? Post it all here.
-
- Posts: 102
- Joined: Tue Aug 19, 2014 12:04 pm
Using Saxon 9.7 and XSLT 3.0 and output method="adpative"
Post 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
inside of oXygen outputs
in the result pane while Saxon run from the command line outputs the correct array syntax
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>
Code: Select all
1 2 3
Code: Select all
[1,2,3]
-
- Posts: 1016
- Joined: Wed Nov 16, 2005 11:11 am
Re: Using Saxon 9.7 and XSLT 3.0 and output method="adpative"
Post 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
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
Jump to
- Oxygen XML Editor/Author/Developer
- ↳ Feature Request
- ↳ Common Problems
- ↳ DITA (Editing and Publishing DITA Content)
- ↳ SDK-API, Frameworks - Document Types
- ↳ DocBook
- ↳ TEI
- ↳ XHTML
- ↳ Other Issues
- Oxygen XML Web Author
- ↳ Feature Request
- ↳ Common Problems
- Oxygen Content Fusion
- ↳ Feature Request
- ↳ Common Problems
- Oxygen JSON Editor
- ↳ Feature Request
- ↳ Common Problems
- Oxygen PDF Chemistry
- ↳ Feature Request
- ↳ Common Problems
- Oxygen Feedback
- ↳ Feature Request
- ↳ Common Problems
- Oxygen XML WebHelp
- ↳ Feature Request
- ↳ Common Problems
- XML
- ↳ General XML Questions
- ↳ XSLT and FOP
- ↳ XML Schemas
- ↳ XQuery
- NVDL
- ↳ General NVDL Issues
- ↳ oNVDL Related Issues
- XML Services Market
- ↳ Offer a Service