> I was looking at the classloader documentation in cvs at
> catalina/docs/dev/classloaders.html and comparing it to
> how Tomcat 4 actually sets up the classloaders. I found
> some discrepancies.
>
> According to the docs the System class loader (CLASSPATH)
> has bin/bootstrap.jar and $JAVA_HOME/lib/tools.jar. But in
> catalina.sh bin/servlet.jar and bin/naming.jar are also added.
>
> According to the docs the Common class loader includes
> bin/servlet.jar and bin/naming.jar, but these are already in
> the System classpath. What need is their to create another
> layer of class loading using the Common class loader if it
> is duplicating jar files already in the class path. Perhaps
> the Common class loader could be removed?
-1. I suggest fixing the catalina.sh script instead. The catalina.bat script
doesn't include any of these in its classpath.
> In the docs the Server class loader includes all jar files in
> /server, but when the class loader is created, it also adds
> /classes if it exists.
>
> The Shared class loader includes all jar files in /lib, as documented.
>
> Question?
>
> What if I have some API I want to install that is shared by web
> applications, but this API needs to use a properties file?
JAR it :) Ok, that's not very convinient, but it works.
Maybe we could add a lib/classes/ path to the shared classloader.
> There
> is no place to install it. Perhaps we could remove /classes from
> the Server class loader and add it instead to the Shared class loader.
Remy
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, email: [EMAIL PROTECTED]
