From: Kevin Ross (Kevin.Ross@iVerticalLeap.com)
Date: Mon Apr 28 2003 - 19:36:27 PDT
I wanted to make sure the environment was good...it is:
[java] Relevant properties:
[java] ==========================================
[java] com.renderx.xep.VALIDATE: false
[java] com.renderx.xep.ROOT: E:\tools\XEP-3.3.1
[java] java.endorsed.dirs: c:\jacobson\lib
[java] javax.xml.transform.TransformerFactory:
org.apache.xalan.processor.TransformerFactoryImpl
[java] javax.xml.parsers.SAXParserFactory:
org.apache.xerces.jaxp.SAXParserFactoryImpl
[java] Class.forName() JAXP transformer and parser:
[java] ==========================================
[java] javax.xml.transform.TransformerFactory: class
org.apache.xalan.processor.TransformerFactoryImpl
[java] javax.xml.parsers.SAXParserFactory: class
org.apache.xerces.jaxp.SAXParserFactoryImpl
-K
-----Original Message-----
From: owner-xep-support@www.renderx.com
[mailto:owner-xep-support@www.renderx.com] On Behalf Of Kevin Ross
Sent: Monday, April 28, 2003 9:10 PM
To: xep-support@renderx.com
Subject: RE: [xep-support] XEP 3 + XALAN
My initial message still hasn't shown yet, so here are my findings so
far:
Xep.bat uses com.renderx.xep.XSLDriver, so I took a look at
transform.bat, and saw the com.renderx.xep.JAXPDriver.
I've altered the script to use the JAXPDriver, but, same exception,
different stack trace:
[java] java.lang.NoClassDefFoundError:
com/jclark/xsl/sax/XSLProcessorImpl
[java] at com.renderx.xep.Driver.init(Driver.java:30)
[java] at
com.renderx.xep.JAXPDriver.<init>(JAXPDriver.java:189)
[java] at
com.renderx.xep.JAXPDriver.<init>(JAXPDriver.java:163)
[java] at com.renderx.xep.JAXPDriver.main(JAXPDriver.java:130)
[java] Exception in thread "main"
Here's the parameters:
[java] Executing 'C:\Program Files\Java\j2re1.4.1_01\bin\java.exe'
with arguments:
[java] '-Djava.endorsed.dirs=c:\jacobson\lib'
[java] '-Xmx256m'
[java] '-Dcom.renderx.xep.VALIDATE=false'
[java] '-Dcom.renderx.xep.ROOT=E:\tools\XEP-3.3.1'
[java]
'-Djavax.xml.transform.TransformerFactory=org.apache.xalan.processor.Tra
nsformerFactoryImpl'
[java]
'-Djavax.xml.parsers.SAXParserFactory=org.apache.xerces.jaxp.SAXParserFa
ctoryImpl'
[java] '-classpath'
[java]
'E:\tools\XEP-3.3.1\lib\cryptix32-pgp.jar;E:\tools\XEP-3.3.1\lib\cryptix
32.jar;E:\tools\XEP-3.3.1\lib\xep331_client_stamped.jar;C:\jacobson\lib\
xalan-2.5.0.jar;C:\jacobson\lib\xerces-2.4.0.jar;C:\jacobson\lib\xml-api
s.jar'
[java] 'com.renderx.xep.JAXPDriver'
[java] '-xml'
[java] 'c:\jacobson/bin/print/input.xml'
[java] '-xsl'
[java] 'c:\jacobson/templates/batch/batchRouteAndPick.xsl'
[java] '-out'
[java] 'c:\jacobson/bin/print/output.pdf'
[java] '-format'
[java] 'PDF'
[java]
[java] The ' characters around the executable and arguments are
[java] not part of the command.
Any help is welcome,
Kevin Ross
-----Original Message-----
From: owner-xep-support@www.renderx.com
[mailto:owner-xep-support@www.renderx.com] On Behalf Of Alexander
Peshkov
Sent: Friday, April 04, 2003 6:02 AM
To: idealcms@gmx.de
Subject: Re: [xep-support] XEP 3 + XALAN
Hello Jan,
XEP is JAXP-aware: it is therefore possible to replace Saxon with
Xalan. Presuming that you use the latest Xalan (2.5), you will need
the following modifications in xep.bat:
- in the classpath, replace saxon.jar by jars from Xalan:
xalan.jar, xercesImpl.jar, and xml-apis.jar;
- add system properties to the Java call. to pick Xalan as the default
XSLT processor and Xerces as the default parser:
-Djavax.xml.transform.TransformerFactory=
org.apache.xalan.processor.TransformerFactoryImpl
-Djavax.xml.parsers.SAXParserFactory=
org.apache.xerces.jaxp.SAXParserFactoryImpl
Best regards,
Alexander Peshkov mailto:peshkov@renderx.com
RenderX
igd> Hi,
igd> is there a possibility to use XALAN (extensions) with XEP 3+?
igd> Kind regards,
igd> Jan
-------------------
(*) To unsubscribe, send a message with words 'unsubscribe xep-support'
in the body of the message to majordomo@renderx.com from the address
you are subscribed from.
(*) By using the Service, you expressly agree to these Terms of Service
http://www.renderx.com/tos.html
-------------------
(*) To unsubscribe, send a message with words 'unsubscribe xep-support'
in the body of the message to majordomo@renderx.com from the address
you are subscribed from.
(*) By using the Service, you expressly agree to these Terms of Service
http://www.renderx.com/tos.html
-------------------
(*) To unsubscribe, send a message with words 'unsubscribe xep-support'
in the body of the message to majordomo@renderx.com from the address
you are subscribed from.
(*) By using the Service, you expressly agree to these Terms of Service http://www.renderx.com/tos.html
This archive was generated by hypermail 2.1.5 : Mon Apr 28 2003 - 19:27:52 PDT