I think you need to do the converse of what you did.
You removed jaxp.jar from Tomcat/lib and then added jaxp.jar to
all the WEB-INF/lib directories of the context directories that
needed it. Have you tried replacing the jaxp.jar in Tomcat/lib
with the latest version that supports namespaces?
Tomcat needs jaxp.jar to parse the config files that are in xml
format. So give Tomcat the latest version so that it is used
both by Tomcat and your code.
-Keith
-----Original Message-----
From: Manuel Melle Ocariz [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, May 22, 2001 11:32 AM
To: [EMAIL PROTECTED]
Subject: classpath
Hi all,
I'm still having problems with classpath setting so I'll explain my particular case:
I have two apps that use different versions of xalan and xerces. In this jar files there is a "javax.xml.parsers.SAXParser" class. I'm trying to deploy them into Tomcat 3.2.1 but when I try to run the one with the newest version I get the following message:
javax.xml.transform.TransformerConfigurationException: Namespace not supported by SAXParser at org.apache.xalan.processor.TransformerFactoryImpl.newTemplates(TransformerFactor
yImpl.java:815)
I found out this was because in TOMCAT's jaxp.jar file there's an elder version of this SAXParser.class. So I thought the only way of solving this was loading different versions for each app and removing the one resident in %TOMCAT_HOME%\lib, but when I tryed to restart TOMCAT it didn't work. I guess this is becouse TOMCAT needs an XML parser to parse all xml-based configuration files, so I feel forced to chose from one of the two versions, for though you can specify new jars to add to the app's classpath, is the first one loaded the one used at runtime.
Any idea (appart from a new TOMCAT for each app)?
Thanks in adv
Manuel Melle Oc�riz
Software AG - E-Business Competence Center
[EMAIL PROTECTED]
