xmlgraphics-fop-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Simon Pepping <spepp...@leverkruid.eu>
Subject Re: Saxon - XSLT 2.0 and Apache FOP
Date Wed, 31 Dec 2008 12:44:59 GMT
This can be achieved by manipulating your classpath. If you ensure
that saxon's jar file is before xalan in the classpath, the correct
definition as quoted below is ensured automatically. This is achieved
because the jar file has this setting in its META-INF/services

The same is true for your selection of the parser. If your class path
contains xerces, saxon and then some other jars, you get xerces for a
parser and saxon for XSLT engine. This is documented in the JAXP


On Mon, Dec 29, 2008 at 09:19:41PM +0100, Andreas Delmelle wrote:
> On 29 Dec 2008, at 21:06, bonekrusher wrote:
>> Ohhh... I didn't know this was possible. From the commandline, how do 
>> you
>> set the property?
> The java command-line switch would be:
> -Djavax 
> .xml.transform.TransformerFactory=net.sf.saxon.TransformerFactoryImpl
> Checking the fop.bat script, you could alter the %JAVA_OPTS% environment 
> variable to have the above switch appended to the command-line.
> Andreas

Simon Pepping
home page: http://www.leverkruid.eu

View raw message