OK, I did search the archive for this question, and did find a (albeit short)
discussion.
1)
What I'd like to have is 1 installation of tomcat running multiple instances (think
each instance is a release), each instance running multiple web applications. I'd
like to have some non-tomcat code common across all webapps in an instance, but not
across all instances.
In this case, I still want CATALINA_HOME to be searched (for Tomcat code), but *also*
CATALINA_BASE/lib and CATALINA_BASE/classes for *instance* code.
If in fact this can't be done, then
http://jakarta.apache.org/tomcat/tomcat-4.0-doc/RUNNING.txt
should be updated in section 4 describing what to do for that situation. (what to
copy from CATALINA_HOME to new CATALINA_HOME)
2)
Reference:
http://jakarta.apache.org/tomcat/tomcat-4.0-doc/class-loader-howto.html
indicates use of CATALINA_HOME/classes and CATALINA_HOME/lib
http://jakarta.apache.org/tomcat/tomcat-4.1-doc/class-loader-howto.html
indicates use of CATALINA_HOME/shared/classes and CATALINA_HOME/lib
jasper-compiler.jar - is under common/lib
jasper-runtime.jar - is under common/lib
naming-factory.jar - is under common/lib
Shouldn't these be in shared/lib (logically) or /lib (according to the docs)?
Mitchell Evan Marx [EMAIL PROTECTED]
AT&T IP Network Configuration & Provisioning Development
Phone: 732-420-2350
Pager: 1-888-858-7243 PIN 134940
http://storefront.metrocall.com/metrocall/sendamsg.asp
Date: Wed, 17 Oct 2001 09:08:27 -0700 (PDT)
From: "Craig R. McClanahan" <[EMAIL PROTECTED]>
Subject: Re: Tomcat 4 shared classloader: possible bug
Content-Type: TEXT/PLAIN; charset=US-ASCII
On Wed, 17 Oct 2001, William Au wrote:
> Date: Wed, 17 Oct 2001 08:56:30 -0400
> From: William Au <[EMAIL PROTECTED]>
> Reply-To: [EMAIL PROTECTED]
> To: [EMAIL PROTECTED]
> Subject: Tomcat 4 shared classloader: possible bug
>
> Shouldn't the shared classloader of Tomcat 4 look in CATALINA_BASE/classes
> and CATALINA_BASE/lib instead of CATALINA_HOME?
> That would allow each instance to use a different version of the common jar
> files.
>
The basic philosophy was that shared JARs would be shared across all uses
of Tomcat, so the "/lib" and "/common/lib" directories are resolved
against CATALINA_HOME instead of CATALINA_BASE. IMHO, this makes sense
given that the whole idea of CATALINA_HOME/CATALINA_BASE is to share
things.
If you want to use a different version of a JAR in a particular webapp,
simply put the JAR in /WEB-INF/lib of that webapp. Or, just run
completely independent installations of Tomcat and you can have your own
"lib" directory.
> Bill
>
>
>
Craig
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
