> -----Original Message----- > From: Caldarale, Charles R [mailto:chuck.caldar...@unisys.com] > Sent: Wednesday, September 23, 2009 7:24 AM > To: Tomcat Users List > Subject: RE: jars in common/lib directory Vs webapps/APP_NAME/WEB- > INF/lib > > > From: V Jayakumar [mailto:v...@hotmail.com] > > Subject: jars in common/lib directory Vs webapps/APP_NAME/WEB-INF/lib > > > > 1) Instead of including these jar files as part of the > > applicationX.war, can they be copied to $CATALINA_HOME/common/lib > > Yes, but it's usually a bad idea to do so. Note that you would not > copy them, you have to move them - you don't want the jars to be in > more than one place in a given branch of the classloader tree. By > placing jars in a common location, you are likely preventing reload of > individual webapps and you creating a versioning dependency nightmare. > > > 2) What is the significance of $CATALINA_HOME/common/lib & > > $CATALINA_HOME/webapps/appName/WEB-INF/lib > > Read the doc: > http://tomcat.apache.org/tomcat-5.5-doc/class-loader-howto.html > > - Chuck >
The referenced document is incomplete because it doesn't say that you can modify the class loader behavior by editing $CATALINA_BASE/conf/catalina.properties. The one case I can say where this may be desirable is log4j. Because of dependencies, log4j.jar has to go in common/lib, and log4j.properties has to go into common/classes. My reading of the catalina.properties file is I could create my own common/lib and common/classes directories and put them into the common class loader by editing the catalina.properties file. George Sexton MH Software, Inc. http://www.mhsoftware.com/ Voice: 303 438 9585 --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
