tomcat-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Bill Barker" <>
Subject Re: classloader issues using ../common/lib vs. ../shared/lib
Date Tue, 04 Feb 2003 08:40:58 GMT
Except for stuff like jdbc drivers, 90% of the time you will see no
difference between common/lib and shared/lib.  The difference is that the
internal Tomcat classes can see what is in common/lib (which the above
mentioned 90% of the time means that they could care less :).

"Mark" <> wrote in message
> Are there any potential classloader problems with putting .jar files that
> are shared across webapps (ie. junit, cactus, etc) in ../common/lib vs.
> ../shared/lib?
> We've been tossing .jars into ../common/lib, but after reading the Tomcat
> classloader how-to it seems that's discouraged, ie. should be done only
> when the classes are needed both by Tomcat and applications such as db
> drivers for JDBC realm and application use. I'm guessing, but does putting
> the .jars in ../shared/lib would spread work out better between
> Our application and integration tools are working great, but the fact
> not configured the way the how-to suggests concerns me.

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message