Oh I completely agree it is bad practice, but alas I must deal with applications that are not my design and dealing with these conflicts is a royal pain in my non-royal ass.
Michael Oliver CTO Alarius Systems LLC 6800 E. Lake Mead Blvd, #1096 Las Vegas, NV 89156 Phone:(702)643-7425 Fax:(702)974-0341 *Note new email changed from [EMAIL PROTECTED] -----Original Message----- From: Caldarale, Charles R [mailto:[EMAIL PROTECTED] Sent: Thursday, May 05, 2005 1:29 PM To: Tomcat Users List Subject: RE: Common vs. Shared > From: Michael Oliver [mailto:[EMAIL PROTECTED] > Subject: Common vs. Shared > > What is the difference between the /common/ and /shared/ > > I understand this is a class loader issue, and I have read > the comments in catalina.properties. But have you read the actual documentation? In particular: http://jakarta.apache.org/tomcat/tomcat-5.5-doc/class-loader-howto.html including this rather descriptive diagram: Bootstrap | System | Common / \ Catalina Shared / \ Webapp1 Webapp2 ... > If a jar is in /common/lib/ and a different version of that > jar is in /shared/lib/ what will be the effect? Trouble, usually. Anytime you have the same class files in multiple places in a single path in the hierarchy, you run the risk of conflicts and lots of NCDFE problems. Very, very bad practice. - Chuck THIS COMMUNICATION MAY CONTAIN CONFIDENTIAL AND/OR OTHERWISE PROPRIETARY MATERIAL and is thus for use only by the intended recipient. If you received this in error, please contact the sender and delete the e-mail and its attachments from all computers. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
