2012/3/13 Christopher Gross <cogr...@gmail.com>:
> Hi all.
>
>  I'm trying to utilize the common/lib and shared/lib directories on
> Tomcat 5.5.25.  I have a few separate apps that were each using many
> of the same JAR files, so I have been moving them down to shared &
> common lib (DB stuff went to common/lib, the apache commons modules &
> others went to the shared/lib).  I was doing testing as I went along
> -- but I never went to look at the logfiles for my webapps.  I'm now
> noticing that they aren't getting anything anymore.  I haven't changed
> anything aside from moving the JARs around.  I'm using the Apache
> Log4j Logger in my classes.
>
>  I have:
> shared/lib:
> commons-logging-1.0.4.jar
> commons-logging-api.jar
> commons-logging.jar
>
> common/lib:
> apache-log4j-extras-1.0.jar
> log4j-1.2.15.jar
>
> each app has:
> commons-logging-1.0.4.jar
> commons-logging-api.jar
> commons-logging.jar
>
> I'd like to avoid rolling back to how everything was, with a lot of
> repeated JAR files all over the place.  Has anyone run into a similar
> problem and found a decent solution?
>

1. You have to read "Class Loading" page of the user manual.

Then I hope that you will note that it is a bad idea to move
everything into common/lib or shared/lib.

2. If you have foo-x.y.z in your libs folder that will impede your
efforts to upgrade some webapps to foo-y.z.w.

Is is better to limit what you put into the common libs folder to
components that are needed by the server itself, like database
drivers.

3. Why are you investing your time in several-years-old 5.5.25,  and
when the whole 5.5.x line is going to be abandoned in several months?

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org

Reply via email to