Because Tomcat 3.2.x uses the CLASSPATH to hold the web server classes (including the XML parser) and uses the JDK delagation model (CLASSPATH classes take priority over WEB-INF classes) web applications can't have a local XML parser. This is one of the reasons both Tomcat 3.3 and Tomcat 4.x make minimal use of the CLASSPATH.
If you stick with Tomcat 3.2.x, you can try replacing jaxp.jar and parser.jar with your XML/XSLT jars. Upgrading Tomcat 3.2.x's XML parser shouldn't cause a problem. In fact, Tomcat 3.2.4 includes JAXP 1.1 (i.e. jaxp.jar and crimson.jar) instead of JAXP 1.0.1 which was included with Tomcat 3.2.1. With Tomcat 3.3, you should have no problem with having your XML/XSLT jars in the WEB-INF/lib. I'm not sure with the various versions of Tomcat 4.x. I think there are a couple of manual steps that are needed to have webapp local XML parsers, but I don't have the exact details in my head yet. Cheers, Larry > -----Original Message----- > From: Christian Kurze [mailto:[EMAIL PROTECTED]] > Sent: Thursday, February 21, 2002 10:40 AM > To: Tomcat-User > Subject: CLASSPATH Tomcat3.2.1 > > > Hi, > following problem: > I want to run a servlet on tomcat3.2.1 which transforms an > xml-document via > xslt into an html-document which should be sent to the > browser. BUT the > packages jaxp.jar and parser.jar are in the tomacat/lib > directory. Whith > these classe ma app doesn't run. So I put new classes in my > WEB-APP/lib > directory. But it won't work, tomcat still uses the 'old' > parser classes. > How could I configure tomcat to use the classes in WEB-INF/lib first? > > If there is another solution for this problem, please tell me. > > thx in advance > Christian > > > -- > To unsubscribe: <mailto:[EMAIL PROTECTED]> > For additional commands: <mailto:[EMAIL PROTECTED]> > Troubles with the list: <mailto:[EMAIL PROTECTED]> > -- To unsubscribe: <mailto:[EMAIL PROTECTED]> For additional commands: <mailto:[EMAIL PROTECTED]> Troubles with the list: <mailto:[EMAIL PROTECTED]>
