Interesting (?) classloader problem

2003-09-03 Thread Jon Skeet
As observant readers will have noticed, I'm migrating a webapp or two from Tomcat 3.2.3 to Tomcat 4.1. Now, our apps have a very specific version of Xerces that they currently need to use (although I'm hoping this requirement will go away). I believe the version is Xerces-J 1.4.4 (at least

RE: Interesting (?) classloader problem

2003-09-03 Thread Cox, Charlie
get the xerces jar, and not the xml classes from other jars. Charlie -Original Message- From: Jon Skeet [mailto:[EMAIL PROTECTED] Sent: Wednesday, September 03, 2003 3:58 AM To: Tomcat User List (E-mail) Subject: Interesting (?) classloader problem As observant readers will have

RE: Interesting (?) classloader problem

2003-09-03 Thread Jon Skeet
There is a typo in the documentation - you can not override the Xerces parser used. Aha. That at least explains my confusion :) You can replace the one in /common/endorsed and see if it works - I don't recall which version tomcat requires. Have you tried your app with the version that

RE: Interesting (?) classloader problem

2003-09-03 Thread Shapira, Yoav
(E-mail) Subject: Interesting (?) classloader problem As observant readers will have noticed, I'm migrating a webapp or two from Tomcat 3.2.3 to Tomcat 4.1. Now, our apps have a very specific version of Xerces that they currently need to use (although I'm hoping this requirement will go away). I