Upgrading to tomcat 4 (or maybe 3.3 as well, I'm not sure what it
does with classpath tho) would do the trick, but I'm not sure if that is
an option. What you are experiencing is a common issue with 3.2, and the
approach you are taking is basically the common fix.
cheers
dim
On Thu, 18 Oct
3.3 will solve this problem.
-Original Message-
From: Dmitri Colebatch [mailto:[EMAIL PROTECTED]]
Sent: Thursday, October 18, 2001 3:00 AM
To: [EMAIL PROTECTED]
Subject: Re: Conflict between tomcat 3.2 libraries and
application libs
Upgrading to tomcat 4 (or maybe 3.3 as well
I am experiencing conflict with libraries in the tomcat\lib directory
and the application\WEB-INF\lib directory.
Specifically the web application needs to use a more recent version of
jaxp.jar than the one deployed with tomcat 3.2 but sees the one in
tomcat\lib first. Updating the one in
