Just so you're aware, if you have a xerces parser (same or another version)
in your webapp/WEB-INF/lib directory, the new ClassLoader configuration
breaks Tomcat, generating a ClassCastException on the xerces
DocumentBuilderFactory implementation when trying to start the JspServlet.
In other words, it appears the change has broken Tomcat. I struggled for 4
days trying to get the 4.0.1 configuration with my web application to work
with absolutely no success. I finally had to use a previous version with
the old jasper directory and ClassLoader scheme to get Tomcat to even start
up with my web application (silly me for trying to use an XML parser). I
have logged this with the bug base but I don't believe anyone believes the
problem exists. All I can say is that my system is up and working under the
old directory structure / class loading scheme and it didn't work before.
I've eliminated all the other variables I can find and it appears the new
ClassLoading is the problem.
Hope that helps the effort. I've temporarily unsubscribed from the Tomcat
user list so please reply directly with further questions.
-the llama
-Original Message-
From: craigmcc@localhost [mailto:craigmcc@localhost]On Behalf Of Craig
R. McClanahan
Sent: Thursday, October 25, 2001 8:30 PM
To: Tomcat User List (E-mail); [EMAIL PROTECTED]
Subject: Re: jasper directory missing in distribution
On Thu, 25 Oct 2001, Joel P. Worrall wrote:
Date: Thu, 25 Oct 2001 09:34:24 -0400
From: Joel P. Worrall [EMAIL PROTECTED]
Reply-To: [EMAIL PROTECTED], [EMAIL PROTECTED]
To: Tomcat User List (E-mail) [EMAIL PROTECTED]
Subject: jasper directory missing in distribution
Is it my imagination or is the jasper directory under CATALINA-HOME
missing
from the 4.0.1 distribution. I am still having an issue with the xerces
parser, so I read the docs on using other XML parsers. The docs mention
removing files from the jasper directory, but when I download the
jakarta-tomcat-4.0.1.tar.gz, the jasper directory does not exist/is not
included.
Why?
The switch to using Xerces as the standard parser eliminated the need for
a separate jasper subdirectory and class loader. Jasper will use
whatever parser is in common/lib or lib (which must be JAXP/1.1
compliant).
Craig
