Hi,
I need to use XSLT as part of a XProc pipeline, so that route is not practicable for me. In that case, you can try to tweak the Calabash engine configuration to use your version of Saxon. First, you may want to read this: https://www.oxygenxml.com/pipermail/oxygen-user/2013-March/004558.html So, you can attempt this by duplicating the engine folder (Oxygen\lib\xproc\calabash) first and customizing the duplicate (make sure the name is different) in engine.xml.
Copy your new Saxon jars to Oxygen\lib\xproc\<calabash_folder>\lib and edit the 'engine.xml' file found a level lower (in Oxygen\lib\xproc\<calabash_folder>). In 'engine.xml' add a new library entry (before the others) for your Saxon jar: <library name="lib/saxon9ee.jar"/> Not sure if the Saxon EE license will hold with this change. You may have to also adjust the 'saxon.config' file and specify @edition="HE". When you configure an XProc transformation, make sure you select your duplicated/customized engine in the "Processor" combo box. Regards, Adrian On 24.12.2015 14:37, Gioele Barabucci wrote:
On 24/12/2015 13:22, Oxygen XML Editor Support (Adrian Buza) wrote:
Hello,
Because of the tight integration (validation, debugging, etc), you cannot upgrade the version of Saxon 9 that comes bundled with Oxygen. Thank you for your response.
I understand that oXygen hooks very deep inside Saxon, but I suppose (maybe naively) that none of these low-level APIs have changed between 9.6.0.7 and 9.6.0.8.
However, you can use a different version of Saxon in Oxygen as a custom (command line) XSLT or XQuery engine for transformations (NOT for debugging), I need to use XSLT as part of a XProc pipeline, so that route is not practicable for me.
Regards,
-- Adrian Buza oXygen XML Editor and Author Support Tel: +1-650-352-1250 ext.2020 Fax: +40-251-461482