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: http://nagoya.apache.org/bugzilla/show_bug.cgi?id=6374 (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. Jake At 09:03 AM 4/2/2002 +0200, you wrote: >Hello, > >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: <mailto:[EMAIL PROTECTED]> >For additional commands: <mailto:[EMAIL PROTECTED]> >Troubles with the list: <mailto:[EMAIL PROTECTED]>
