I'm part of an infrastructure team that hosts corporate web-apps on behalf
of our developers and we provide and maintain a Tomcat 6.0.x bundle for
them to use. Our bundle contains a set of lifecycle-listeners that employ
log4j, activemq and various other libraries that can clash with those
supplied by our developers. For example, we'll supply activemq-5.3.0 and
they'll supply activemq-4.1.1 which is ok because the respective brokers
are completely separate.
My aim is to arrive at a general Tomcat configuration that does a great
job of isolating infrastructure and developer libraries from one another
so that both teams are as free as possible to supply libraries with no
fear of conflicts. In addition to adhering to best-practices related to
'WEB-INF/lib' and 'lib' directories, it seems to me that enabling the
server loader will be needed to accomplish this. Here's what I have so
far:
common.loader=${catalina.base}/lib,${catalina.base}/lib/*.jar,${catalina.home}/lib,${catalina.home}/lib/*.jar
server.loader=${catalina.home}/server/*.jar
shared.loader=
I'm referring to Tomcat 5.5 docs to guide what JARs would migrate from
'lib' to 'server'. I'm also aware of the "privileged" context attribute
and its effect of selecting the parent classloader, but I want to use it
judiciously. If it helps keep things simple, let's assume a Tomcat
instance hosts no more than 1 application.
Any guidance on this objective would be greatly appreciated,
Edwin
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org
