Well then, you have to copy the jar to the WEB-INF/lib of your webapp. Beyond that, for forcing Qizx or JAXP to use a XSLT jar, there is a system property javax.xml.transform.TransformerFactory that controls the XSLT implementation, but how to specify it can be platform-dependent, so I cannot be more precise than that. You have to refer to the appropriate documentation.
Cheers On Thu, 05 Apr 2012 09:43:01 +0200, Roman Klein <[email protected]> wrote: > Hello Xavier, > > Thanks for your answer, but ..... mmhh > > Assuming that the x:transform() function is executed server-side, > I'd expect to add the saxon-jar to the server classpath e.g. > <jetty>/lib/ext or <tomcat>/lib/endorsed > and optionally, additionally add some property setting > to guide the server to use sf.net.saxon.TransformerFactoryImpl > instead of org.apache.xalan.processor.TransformerFactoryImpl > > Following your approach I do get errors stating the v2.0-stylesheet > could not be compiled. > The error messages are indicating that still the standard xslt-processor > is used. > The stylesheet itself is working as I do use it in Orbeon forms > sucessfully. > A v1.0-stylesheet is properly processed. > > Following my above mentioned approach I do get an unspecified error: > Failed to compile stylesheet. 1 error detected. > This error occurs for v1.0 and v2.0-stylesheets, > I therfore assume that the saxon as such is not properly recognized. > > How can I increase the verbosity of error messages, in which log-file > can detailed > error messages been seen? > > Best Regards > Roman Klein > -- Xavier Franc Qizx design and development -- Qizx Support List [email protected] http://www.xmlmind.com/mailman/listinfo/qizx-support
