Configuring OxygenXML to use the same XSLT processor as Sakai

When developing a stylesheet for a Sakai/OSP portfolio template, you ideally want your IDE to transform your passthrough XML with the same version of Xalan as Sakai. My version of OxygenXML is using Xalan 2.7, but Sakai is still stuck on Xalan 2.6. I've heard other template developers complain that their stylesheet works in OxygenXML, but fails in Sakai. Its easy to rule out this possible source of error by trying out your stylesheet with the right version of Xalan from the command line, but it is pretty easy to can set a "Custom Engine" in the OxygenXML preferences that will allow you transform your passthrough right in the IDE.

In preferences, under XML > XSLT-FO-QUERY > Custom Engine, you can add your own custom engine. Give it a name (Xalan 2.6.0) and add the following the "command line" setting.

java -jar /home/you/.m2/repository/xalan/xalan/2.6.0/xalan-2.6.0.jar -IN ${xml} -XSL ${xsl} -OUT ${out}

Click OK and save the preferences. From then on, you will be able to choose Xalan 2.6.0 as a tranformation engine in your transformation scenarios.

This allows you to change versions of OxygenXML or Sakai and still be able to use the right engine for your scenario.