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
After thinking about this some more I have a proposal to change the
Tomcat 4 class loading.
The class loaders that Catalina uses are organized as follows, where
the parent class loader is above the child class loaders:
Bootstrap
|
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
The above changes remove one class loading layer from a web app,
allows Common classes to use property files and resources, and cleans
up the directories where jar files and classes are located.
The Catalina core would see the shared libraires, which is a very bad idea
IMO. We'll get into the
Hello,
I find even if I don't include .\tomcat\lib\webserver.jar
into my CLASSPATH, I can still start tomcat server and execute
the servlet file through browser.
Would you please let me know what functions are in webserver.jar
and when I have to include it in CLASSPATH?
I'll appreciate to get
Remy Maucherat wrote:
The above changes remove one class loading layer from a web app,
allows Common classes to use property files and resources, and cleans
up the directories where jar files and classes are located.
The Catalina core would see the shared libraires, which is a very bad
Remy Maucherat wrote:
Thats right! Ok, I retract my proposal for changing the class loaders.
What we can do is add a lib/classes/ repository to the shared
classloader.
I still think it would be a good idea to change the directory structure of
where the lib/classes are located to make it
Tal Dayan wrote:
The Tomcat 3.2 standalone does not seem to support http status code 304
('if-modified-since', code SC_NOT_MODIFIED) and is always sending back the
entire file, even it has not been modified.
Is it going to be supported by versions '3.3' or 4.0 ?
Tomcat 4.0 *does* support
Remy Maucherat [EMAIL PROTECTED] wrote:
Quoting Jason Brittain [EMAIL PROTECTED]:
Please let me know when you're ready to discuss my TomcatBlock
patches.. No hurry on my part, I just want to keep the idea warm. :)
Feel free to see it in action at:
http://eas.betaversion.org
I
craigmcc01/02/17 18:18:15
Modified:.build.xml
catalina/src/share/org/apache/catalina/core
StandardWrapper.java
catalina/src/share/org/apache/catalina/loader
StandardClassLoader.java
craigmcc01/02/17 19:33:48
Modified:catalina/docs/dev classloaders.html
Log:
Update the documentation on Catalina's class loader hierarchy to reflect the
changes recently made in how Jasper is loaded.
Revision ChangesPath
1.3 +96 -46
11 matches
Mail list logo