See comments from Remy Maucherat in the following bugs:

http://nagoya.apache.org/bugzilla/show_bug.cgi?id=6374
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=6248

There were classloader changes in 4.0.2 (same in 4.0.3) that causes the 
webapp classloader to not load xml and dom classes.  It is apparently 
forbidden to do this except in the parent classloader 
(TOMCAT_HOME/common/lib or jdk1.4/jre/lib/endorsed or instance).   However, 
the changes there were not, apparently, overly intelligent.  He fixed that 
on the tip (tomcat-dev-4.1) and said that it might not ever be implemented 
in 4.0.x releases.  However, it is in 4.0.4-b2, so 4.0.4 will be better 
about this.

However, you still won't be able to have your xml parser inside 
WEB-INF/lib.  Better learn to live with it in
TOMCAT_HOME/common/lib or jdk1.4/jre/lib/endorsed because that is where it 
will have to be now and forever (in the forseeable future, that is).

Jake

At 12:08 PM 4/19/2002 +1000, you wrote:
>This might be a newbie question, but is there anything special I need to do
>(eg. an entry in the web.xml deployment descriptor) to put my third party
>JAR files in the WEB-INF/lib directory instead of Tomcat's common/lib
>directory? I can't find anything in the documentation about Tomcat 4.0.3 is
>running standalone on our system.
>
>The jar file has classes to do xml messaging across a network and therefore
>has XML parsing classes in it. Whenever I put the jar file in the
>WEB-INF/lib directory I get a NoClassDefFoundError on one of the custom
>classes (not an xml parsing class), yet it works fine in Tomcat's common/lib
>directory even after restarting the server on both tests. The problem may be
>a class loading conflict between Tomcat's XML classes and the third party
>XML classes but I'm not sure.
>
>Could someone enlighten me on what else could be the problem and/or explain
>any class loading issues?
>
>Thanks,
>
>Tony McGee
>Australink.net
>
>
>
>
>--
>To unsubscribe:   <mailto:[EMAIL PROTECTED]>
>For additional commands: <mailto:[EMAIL PROTECTED]>
>Troubles with the list: <mailto:[EMAIL PROTECTED]>

Reply via email to