Page 1 of 1

Continuous integration for XML to PDF

Posted: Tue Apr 28, 2015 10:58 am
by odinodin
Hi,
We're currently looking in to the possibility of building our documents in a continuous integration solution, i.e generating pdfs automatically every time someone does a commit. This will help us find issues early and improve our process. The FO to PDF process we have good information about, but not how Oxygen transforms XML to FO.

How can we run the same XSLT-transformation command that Oxygen does from the command line?

Basically I'd like to see the java command that is run by Oxygen under the hood for transforming XML to an FO-file.

Re: Continuous integration for XML to PDF

Posted: Tue Apr 28, 2015 11:19 am
by Radu
Hi,

To run from the command line XSLT 2.0 processing you can download separately the Saxon 9 XSLT processor:

http://www.saxonica.com/welcome/welcome.xml

and read its getting started section:

http://www.saxonica.com/documentation/i ... tartedjava

Regards,
Radu

Re: Continuous integration for XML to PDF

Posted: Wed May 06, 2015 11:43 am
by odinodin
So we're using Saxon 6.5.5 to transform XML to an FO-file.

Is there any way to see which java-command that Oxygen runs when transforming?

Is there any way to get any log output from this process?

Re: Continuous integration for XML to PDF

Posted: Wed May 06, 2015 12:13 pm
by adrian
Hi,

Oxygen doesn't run a Java command when applying a Saxon transformation, it uses the Saxon Java API (because Oxygen itself is a Java application). Consequently there's no log output.

You can find the command line information on the Saxon 6.5.5 page:
http://saxon.sourceforge.net/saxon6.5.5/
java -cp saxon.jar;saxon-xml-apis.jar com.icl.saxon.StyleSheet source.xml stylesheet.xsl

If you have Java extensions (.jar) that are used for the transfromation, simply add them to the classpath from the command line:
java -cp saxon.jar;saxon-xml-apis.jar;my-extension.jar ...

Note that on Linux and Mac the classpath separator is ':' instead of ';'.

Regards,
Adrian