Kevin Ross wrote: > I successfully started over again with a fresh installation of Tomcat > 4.1.12-LE, uncovering another side effect of the tomcat classloader. I > find that the ClassLoader-HOWTO is very vague in explaining the exact > boundaries of the classloaders...here's why: > > To make it work: > moved commons-beanutils, and commons-logging to common/lib from > server/lib, these were duplicated before because I didn't understand > (more like pay attention) the server can use resources from there. I > believe this caused come kind of mismatch in the classloader when > testing isAssignableFrom(). Copied the commons-digester to my web-app > (my app code uses it and the other commons packages). > > The problem: I shouldn't need to put the commons-digester.jar in BOTH > the server/lib, and my webapp/WEB-INF/lib, when I can place it in the > commons/lib. But, doing just that, tomcat fails to start. Though the > writeup on the classloaders helps a lot, it doesn't explain why the > commons-digester.jar has to be in the server/lib ONLY for catalina to > start. > > I assume this is a bug? If so, please let me know and I'll put it in > bugzilla.
Don't bother. Whatever CL problems are left in TC 4.1 (I assume it will be only tricky cases) won't be fixed. In 5.0, I'll be pushing to use standard Java 2 delegation, and the problems should go away. Remy -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
