This is a simple question, but one I cannot find the answer to. I have an XSLT 2.0 stylesheet that I’m trying to process in Java. It relies on XSL elements from Saxon.
My current class works fine with simple XSLT 1.0, but I’m getting errors about unrecognized elements with my 2.0 XSLT built with Saxon.
I cannot figure out how to tell Java to use Saxon as the processor. I’m using javax.xml.transform in my class. Is this a property I can set? What do I set it to? Thanks!
Edited I figured out how to set the property to use Saxon, but now I’m getting this error.
Provider net.sf.saxon.TransformerFactoryImpl not found
How do I include Saxon in my application?
There are multiple ways to do this (in order of lookup precedence):
Explicitly instantiate the Saxon factory (with a nod to Michael’s comment above):
TransformerFactory fact = new net.sf.saxon.TransformerFactoryImpl()
This approach means that your code is locked into using Saxon at compile time. This can be seen as an advantage (no risk of it running with the wrong processor) or a disadvantage (no opportunity to configure a different processor at execution time – not even Saxon Enterprise Edition).
For Saxon-PE, substitute
com.saxonica.config.ProfessionalTransformerFactory. For Saxon-EE, substitute
Specify Class Name
Specify the factory class when constructing it:
TransformerFactory fact = TransformerFactory.newInstance( "net.sf.saxon.TransformerFactoryImpl", null);
This approach allows you to choose the processor at execution time, while still avoiding the costs and risks of a classpath search. For example, your application could provide some configuration mechanism to allow it to run with different Saxon editions by choosing between the various Saxon factory classes.
Use System Property
javax.xml.transform.TransformerFactory system property before creating an instance:
Or on the command line (line broken for readability):
java -Djavax.xml.transform.TransformerFactory= net.sf.saxon.TransformerFactoryImpl YourApp
This approach has the disadvantage that system properties affect the whole Java VM. Setting this property to select Saxon could mean that some other module in the application, which you might not even know about, starts using Saxon instead of Xalan, and that module could fail as a result if it uses Xalan-specific XSLT constructs.
Use Properties File
Create the following file:
With the following contents:
This approach has similar consequences to using the system property.
Create the following file in any JAR on the CLASSPATH:
With the following contents:
This approach has the disadvantage that a small change to the classpath could cause the application to run with a different XSLT engine, perhaps one that the application has never been tested with.
If none of the above are done, then the platform default
TransformerFactory instance will be loaded. A friendly description of this plugability layer can be found here.
Note that ‘platform’ here means the Java VM, not the hardware or operating system that it is running on. For all current known Java VMs, the platform default is a version of Xalan (which only supports XSLT 1.0). There is no guarantee that this will always be true of every Java VM in the future.
I’d consider this answer an argument against the Java way of doing things.