> This shouldn't be true. Apps cannot see the system classpath at all. > Only Tomcat sees that at startup. Webapps will only see classes in > WEB-INF/lib, WEB-INF/classes, common/endorsed, common/lib, > common/classes, shared/lib, and shared/classes. Tomcat, itself, also > sees stuff in server/lib and server/classes.
No Jacob, that's not true. Classes within the Tomcat container have full visibility of the system classpath. The startup scripts, however, ignore the CLASSPATH environment variable on start up which gives the illusion that Tomcat is not seeing those classes. The reason it's not seeing those classes is because of the actions of the startup script, not because of the Tomcat container itself. All of the classloaders descend from the original classloader used to fire up the Tomcat bootstrap. So, if you start Tomcat up without the provided scripts, or change the scripts to manipulate the CLASSPATH for the JVM, your classes will be able to see those classes. Regards, Will Hartung ([EMAIL PROTECTED]) -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
