>From: Duane Morse
>Subject: Don't try to mix jaxp-1.1ea with Tomcat!
>Date: Thu, 30 Nov 2000 15:52:03 -0700
>I've tried for 3 days to get Tomcat 3.2 (b8 and now the final release to
work with Sun's 1.1 early release of XML parsing software (jaxp-1.1ea),
without success, >so if you're looking for XML parsers to use with your
Tomcat build, don't use these!
>
>Duane Morse, Eldorado Computing Inc., Phoenix Arizona
I am using Tomcat 3.2.1. I can successfully upgrade Tomcat's JAXP to Sun's
JAXP 1.1 Final Release
Just change worker.properties as:
#worker.inprocess.class_path=$(workers.tomcat_home)$(ps)lib$(ps)jaxp.jar
#worker.inprocess.class_path=$(workers.tomcat_home)$(ps)lib$(ps)parser.jar
worker.inprocess.class_path=d:\jaxp-1.1\xalan.jar
worker.inprocess.class_path=d:\jaxp-1.1\jaxp.jar
worker.inprocess.class_path=d:\jaxp-1.1\crimson.jar
And change wrapper.properties as:
#wrapper.class_path=$(wrapper.tomcat_home)\lib\jaxp.jar
#wrapper.class_path=$(wrapper.tomcat_home)\lib\parser.jar
wrapper.class_path=d:\jaxp-1.1\xalan.jar
wrapper.class_path=d:\jaxp-1.1\jaxp.jar
wrapper.class_path=d:\jaxp-1.1\crimson.jar
It can solve the problem that transformation causes
javax.xml.transform.TransformerException: Namespace not supported by
SAXParser. Because tomcat try to use the old JAXP to do transformation.
Also unmarking the old JAXP can prevent from java.lang.SecurityException:
sealing violation, when runing TransformerFactory transformerFactory =
TransformerFactory.newInstance(); . Because the Sun's JAXP 1.1 is packed as
sealed Jar. It should not mix up with the old library....
TAI Wai Wang, Leo
_________________________________________________________
Do You Yahoo!?
Get your free @yahoo.com address at http://mail.yahoo.com
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, email: [EMAIL PROTECTED]
