xslt-process and saxon 6.5
Brought to you by:
ovidiu
From: Benjamin P. <bp...@ze...> - 2001-12-04 07:45:08
|
Hi, is there a way to get xslt-process to work with anything else than saxon 6.3? Well, apart from the debugger, everything is ok, but then that's what's great about xslt-process ;-) To be more detailed: saxon 6.3, which is supplied with xslt-process ahs a show-stopper bug for me. It will return true on a test for a non-existant attribute. I have dropped in saxon 6.5 by simply changing the classpath list in xslt-process.el (and of course placed the jar file in the java dir). (defvar xslt-process-external-java-libraries (mapcar (lambda (f) (concat (xslt-process-find-xslt-data-directory) "java" xslt-process-dir-separator f)) '("bsf.jar" "xerces.jar" "xalan-2.1.0.jar" "saxon-6.5.jar" "xalanj1compat.jar" "batik.jar" "fop-0.20.1.jar" "jimi-1.0.jar" "xslt.jar")) "Defines the classpath to the XSLT processors thyat do the real work of processing an XML document. Be sure you know what you're doing when you modify this.") The debugger will then produce the following stack trace: java.lang.NoClassDefFoundError: com/icl/saxon/om/ElementInfo at xslt.debugger.saxon.SaxonTraceListener.leaveNode(SaxonTraceListener.java:184) at xslt.debugger.saxon.SaxonTraceListener.leave(SaxonTraceListener.java:302) at com.icl.saxon.style.XSLStyleSheet.process(XSLStyleSheet.java:624) at com.icl.saxon.Controller.transformDocument(Controller.java:1065) at com.icl.saxon.Controller.transform(Controller.java:939) at xslt.debugger.AbstractXSLTDebugger.run(AbstractXSLTDebugger.java:188) at java.lang.Thread.run(Thread.java:484) Any help is appreciated. Cheers, Ben |