Return-Path: Delivered-To: apmail-jakarta-tomcat-user-archive@apache.org Received: (qmail 36221 invoked from network); 12 Feb 2002 00:36:33 -0000 Received: from unknown (HELO nagoya.betaversion.org) (192.18.49.131) by daedalus.apache.org with SMTP; 12 Feb 2002 00:36:33 -0000 Received: (qmail 23036 invoked by uid 97); 12 Feb 2002 00:36:05 -0000 Delivered-To: qmlist-jakarta-archive-tomcat-user@jakarta.apache.org Received: (qmail 23007 invoked by uid 97); 12 Feb 2002 00:36:04 -0000 Mailing-List: contact tomcat-user-help@jakarta.apache.org; run by ezmlm Precedence: bulk List-Unsubscribe: List-Subscribe: List-Help: List-Post: List-Id: "Tomcat Users List" Reply-To: "Tomcat Users List" Delivered-To: mailing list tomcat-user@jakarta.apache.org Received: (qmail 22996 invoked from network); 12 Feb 2002 00:36:04 -0000 Message-ID: <24946BD18054D4119BE200D0B73E87778D5F50@BOROMIR> From: Matt Small To: 'Tomcat Users List' Subject: RE: Tomcat 4.0.2 - Startup fails after moving xerces.xml from /co mmon/lib to /server/lib Date: Mon, 11 Feb 2002 16:36:12 -0800 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2650.21) Content-Type: text/plain; charset="iso-8859-1" X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N Actually, I just tried this with a stock 4.0.2 installation. I get the same exception loading the default webapps. Looks like 4.0.2 is a flawed release to me. I'm going to report this as a bug. Matt -----Original Message----- From: Matt Small [mailto:msmall@Clickability.com] Sent: Monday, February 11, 2002 4:21 PM To: Tomcat (E-mail) Subject: RE: Tomcat 4.0.2 - Startup fails after moving xerces.xml from /co mmon/lib to /server/lib Yes, but . . . (1) I am able to successfully do this with 4.0.2-b2. I had catalina xerces 1.4.3 and my webapp using the two 2.0.0 jars. No problems. (2) To make sure that this wasn't a problem with xerces 2.0.0, I rolled my webapp back to using 1.4.3 and rebuilt it. So now with both xerces 1.4.3 in /server/lib and my webapp lib (but not in /common/lib), it still fails. I think that this is a bug with the new release. This is not a huge problem for me because I am really just experimenting with Xerces2, but this may hurt someone else who wants to use a different parser. Should I report it in bugzilla? Thanks Matt -----Original Message----- From: GOMEZ Henri [mailto:hgomez@slib.fr] Sent: Monday, February 11, 2002 4:12 PM To: Matt Small Cc: tomcat-user@jakarta.apache.org Subject: Tomcat 4.0.2 - Startup fails after moving xerces.xml from /common/lib to /server/lib In xerces 2.0.0 the SAX/DOM and Parser are splitted in 2 jars and should be both included in the same lib. Since CL will find part of the SAX/DOM in xerces 1.4.3 jar it may be stucked when you'll ask xerces 2.0 stuff since the 1.4.3 jar will be in scope due to SAX/DOM load. Hope it will help >I am using xerces 2.0.0 in one of my webapps so I need to move xerces.jar >out of /common/lib and into /server/lib. This works just fine with 4.0.2-b2. >With 4.0.2 If I keep xerces.jar in /common/lib and use xerces.jar 1.4.3 in >my web app everything starts up just fine. But if I move xerces.jar into >/server/lib I get the exception below. I suspect that this is due to the >ClassLoader bug fixes done between 4.0.2-b2 and 4.0.2. Is there any >workaround for this? >Thanks for any help. >Matt -- To unsubscribe: For additional commands: Troubles with the list: -- To unsubscribe: For additional commands: Troubles with the list: