There appears to be a serious problem with the classpath/classloader with
Tomcat 3.2.1.
It may be related to the Jasper engine, which outputs a dynamic classpath
name that includes all of the classes and jars in the WEB-INF directory, as
expected. But is the same classloader used when servlets are loaded at
startup according to the web.xml file?
Anyway, I'm not sure where the problem resides, but I have found that by
setting the CLASSPATH to the same thing Jasper sets up (specifically those
files in WEB-INF/classes and WEB-INF/lib), my beans will no longer complain
about unknown classes.
But unfortunately, this "fix" doesn't really work because apparently they
really are loaded by different classloaders, so they are not the same
classes within the JVM. This causes problems for classes that appear to
have been initialized, but then magically are not when loaded through the
other classloader.
Anyway, is there anybody looking into this? I know I've seen several
postings complaining about classpath problems that are likely related to
this. Has it been fixed in 3.2.2?
Thanks,
David
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, email: [EMAIL PROTECTED]
