cvs commit: jakarta-tomcat-4.0/catalina/docs/dev classloaders.html

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 -46jakarta-tomcat-4.0/catalina

cvs commit: jakarta-tomcat-4.0/tester/src/bin tester.bat tester.sh

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 jasp

Re: cvs commit:jakarta-tomcat-4.0/catalina/src/share/org/apache/catalina/startupCatalinaBlock.java CatalinaBlock.xinfo

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.betaver

Re: cvs commit:jakarta-tomcat-4.0/catalina/src/share/org/apache/catalina/startupCatalinaBlock.java CatalinaBlock.xinfo

Jason Brittain <[EMAIL PROTECTED]> wrote: > [EMAIL PROTECTED] wrote: > >> remm01/02/15 18:36:37 >> >> Removed: catalina/src/share/org/apache/catalina/startup >> CatalinaBlock.java CatalinaBlock.xinfo >> Log: >> - Remove the Avalon wrapper. This will be

Re: [PROPOSAL] Tomcat 4 class loaders

Remy Maucherat wrote: > > Note: Craig may veto these changes because we're so late in the dev cycle. > Can you guys please hold off for a while before making *any* changes? I'm right in the middle of trying to make Jasper work without having an XML parser exposed to webapps, and it's going to i

Re: Any plan to support status 304 ?

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* sup

RE: [Bug 486] Changed - ????? instead of content of @include pages when contentType present in root page BugRat Report#817

I just read this and noticed a type in my orginal message. If it wasn't clear from the context I meant to say that I could duplicate the problem in tomcat_321_final. > -Original Message- > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] > Sent: Friday, February 16, 2001 10:13 PM > To:

Re: [PROPOSAL] Tomcat 4 class loaders

Remy Maucherat wrote: > > > 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 o

Re: [PROPOSAL] Tomcat 4 class loaders

> 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

Re: [PROPOSAL] Tomcat 4 class loaders

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

webserver.jar

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 y

AW: [ANNOUNCEMENT] Tomcat 3.3 Milestone 1

> 3) The new class loader scheme in this release ignores your > CLASSPATH setting. >Instead, you are expected to add needed jars to Tomcat's > "lib", "lib/common", >and "lib/shared" directories. See the "README" file in Tomcat's "doc" >directory for details. > It took a while to a

Re: [PROPOSAL] Tomcat 4 class loaders

> 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 t

Re: Tomcat 4 class loaders

> 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

[PROPOSAL] Tomcat 4 class loaders

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 |

Tomcat 4 class loaders

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.ja