How to use Saxon 9.5?
Here should go questions about transforming XML with XSLT and FOP.
-
- Posts: 2879
- Joined: Tue May 17, 2005 4:01 pm
Re: How to use Saxon 9.5?
Hello,
Saxon 9.5 will be bundled with Oxygen v15.0.
Because of the tight integration (validation, debugging, etc), you cannot upgrade (or change to a different edition: HE/EE) the version of Saxon 9 EE (Oxygen/lib/saxon9ee.jar) that comes bundled with Oxygen.
Also note that the edition of Saxon-EE bundled with Oxygen is only licensed to be used within the Oxygen GUI. It cannot be used from the command line without a separate license for Saxon-EE (from Saxonica).
However, you can use a different version of Saxon in Oxygen as an external XSLT engine, though for PE/EE you will need a separate Saxon license. You can configure it in Options > Preferences , XML > XSLT-FO-XQuery > Custom Engines. Press New, select engine type: XSLT and give it a proper name. e.g. "Saxon-EE 9.5".
In the command line of the custom engine use:
java -jar path\to\saxon\lib\saxon9ee.jar "-s:${xml}" "-xsl:${xsl}" "-o:${out}"
(do not omit the quotes)
You can then choose this newly defined engine from the Transformer combo when configuring a transformation scenario: Document > Transformation > Configure Transformation Scenario, New/Edit.
Note that external XSLT engines cannot be used in the debugger.
Let us know if you need further assistance.
Regards,
Saxon 9.5 will be bundled with Oxygen v15.0.
Because of the tight integration (validation, debugging, etc), you cannot upgrade (or change to a different edition: HE/EE) the version of Saxon 9 EE (Oxygen/lib/saxon9ee.jar) that comes bundled with Oxygen.
Also note that the edition of Saxon-EE bundled with Oxygen is only licensed to be used within the Oxygen GUI. It cannot be used from the command line without a separate license for Saxon-EE (from Saxonica).
However, you can use a different version of Saxon in Oxygen as an external XSLT engine, though for PE/EE you will need a separate Saxon license. You can configure it in Options > Preferences , XML > XSLT-FO-XQuery > Custom Engines. Press New, select engine type: XSLT and give it a proper name. e.g. "Saxon-EE 9.5".
In the command line of the custom engine use:
java -jar path\to\saxon\lib\saxon9ee.jar "-s:${xml}" "-xsl:${xsl}" "-o:${out}"
(do not omit the quotes)
You can then choose this newly defined engine from the Transformer combo when configuring a transformation scenario: Document > Transformation > Configure Transformation Scenario, New/Edit.
Note that external XSLT engines cannot be used in the debugger.
Let us know if you need further assistance.
Regards,
Adrian Buza
<oXygen/> XML Editor, Schema Editor and XSLT Editor/Debugger
http://www.oxygenxml.com
<oXygen/> XML Editor, Schema Editor and XSLT Editor/Debugger
http://www.oxygenxml.com
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