I had the same problem and here is the solution that worked for me: (with
Tomcat 3.2)
edit $TOMCAT_HOME/bin/tomcat.bat (or .sh)
Replace the following line:
set CLASSPATH=%CLASSPATH%;%cp%
with
set CLASSPATH=path/to/xerces.jar;%CLASSPATH%;%cp%
where "path/to/xerces.jar" is obviously the path to where you extracted the
xerces package.
This will guarantee that xerces.jar comes before the xml parser included
with Tomcat while leaving the xml parser needed by Tomcat.
Hope this helps.
Gilles
> -----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(Tra
> nsformerFactor
> 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]
>
>
