Message5328

Author amak
Recipients Mekk, amak, fwierzbicki, gturnquist
Date 2009-11-30.14:08:14
SpamBayes Score 6.43021e-07
Marked as misclassified No
Message-id <1259590095.36.0.982195931123.issue1489@psf.upfronthosting.co.za>
In-reply-to
Content
One interesting note in the Tomcat documentation, in relation to
classloading, is this

http://tomcat.apache.org/tomcat-6.0-doc/class-loader-howto.html

"""
As indicated in the diagram above, Tomcat 6 creates the following class
loaders as it is initialized:

  * Bootstrap - [ .. snip ..]
  * System - This class loader is normally initialized from the contents
of the CLASSPATH environment variable. All such classes are visible to
both Tomcat internal classes, and to web applications. However, the
standard Tomcat 6 startup scripts ($CATALINA_HOME/bin/catalina.sh or
%CATALINA_HOME%\bin\catalina.bat) totally ignore the contents of the
CLASSPATH environment variable itself, and instead build the System
class loader from the following repositories:
    o $CATALINA_HOME/bin/bootstrap.jar - Contains the main() method that
is used to initialize the Tomcat 6 server, and the class loader
implementation classes it depends on.
    o $CATALINA_HOME/bin/tomcat-juli.jar - Package renamed Jakarta
commons logging API, and java.util.logging LogManager.
"""

I will be investigating this further.
History
Date User Action Args
2009-11-30 14:08:15amaksetmessageid: <1259590095.36.0.982195931123.issue1489@psf.upfronthosting.co.za>
2009-11-30 14:08:15amaksetrecipients: + amak, fwierzbicki, Mekk, gturnquist
2009-11-30 14:08:15amaklinkissue1489 messages
2009-11-30 14:08:14amakcreate