Saxon

Legacy ID: #4653871 Legacy Poster: Michael Kay (mhkay)

The documentation is here: http://www.saxonica.com/documentation/using-xsl/commandline.html Michael Kay Saxonica

Legacy ID: #4654589 Legacy Poster: pvallone (pvallone)

Thank you Michael, I read through the documentation. What what I read I need to compile the XSLT. I am not sure what this means. Can you provide some guidance? Thanks

Legacy ID: #4654605 Legacy Poster: Michael Kay (mhkay)

I don't know exactly what you read, so I'm not sure exactly what your question is. If you're using the Java or .NET API to control transformation, and if you want to use the same stylesheet more than once, then you have the option to compile it once and execute it repeatedly. This avoids repeating work unnecessarily. The "compiled" stylesheet (which is an internal Saxon representation, it's not actually machine code) is typically held in memory. If you control transformation from the command line, however, compiling and running are combined in a single step. Saxon on Java also provides an option to save the compiled stylesheet to disk, but this gives little performance benefit compared with recompiling the original source, so it has not been implemented on the .NET platform. When you are controlling transformation from an application I would normally recommend using the programmatic API rather than an exec on the command line, unless you really don't care at all about performance.

Legacy ID: #4654725 Legacy Poster: pvallone (pvallone)

Michael, Thank you for your help. You bring up an interesting point about performance. The question about a XSLT stand alone transformations takes a split second. My other transformations of XML to HTML processes about 700+ xml files and does this very fast. If I start getting into performance issues, I'll use the programmatic API. Thanks for the help. Phil