tomcat-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Jacob Kjome <>
Subject Re: Libraries problem
Date Tue, 02 Apr 2002 08:01:28 GMT
Hi Raymond,

Supposedly having the XML parser in the webapp itself is against the Sun 
classloading spec.  The spec was beginning to be implemented in 4.0.2 (in 
fact, if you look at 4.0.2-b2, you still get the 4.0.1 behavior).  4.0.3 is 
pretty much an exact copy of 4.0.2 except with a security fix.  4.0.4 betas 
are starting to get the classloading issues right (before you would see a 
lot of ClassNotFoundExceptions even if the lib was in the proper directory 
in Tomcat outside the webapp).

Here's the official bug on this behavior: (note that it is 
fixed, btw)

Much of this has to do with the fact that j2sdk.4.0 now contains an XML 
parser by default.  You may have noticed the new lite builds without most 
of the libraries since 1.4.0 already includes them.


At 09:03 AM 4/2/2002 +0200, you wrote:

>I use TC 4.0.3, my web app used XML parser and transformer (throught the
>XML Jakarta project FOP).
>Before I was using TC 4.0.1, with this version my application was
>working with all libraries (jar files)
>used to run it who were inside my WEB-INF/lib.
>I do not understand why now I am with TC 4.0.3, I have to put a
>transformer jar (xalan) in my TC/common/lib
>repository ?
>Any indications or documentation about this libraries incluson problem ?
>To unsubscribe:   <>
>For additional commands: <>
>Troubles with the list: <>

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message