Wars are class path isolated -----Original Message----- From: Bruno <[email protected]> Sent: Tuesday, February 10, 2009 1:09 PM To: [email protected] Subject: [cas-user] Dependent library version conflicts - recommended strategy?
I just installed the sample pre-built CAS WAR, which works fine, and I'm about to build/configure so that I can tie it to my apps and ActiveDirectory. I noticed that being deployed as a WAR, it will share the classloader in Tomcat (or jBoss) with other webapps. Since it contains JARs for spring, spring security and others, there is a potential for version conflicts. For example, we currently use spring 2.0.7 and spring-security 2.0.4 instead of spring 2.5.6 and spring-security 2.0.3 included in the cas distribution. Is there a recommended strategy to avoid such conflicts? (other than instantly changing the library versions used by all of our apps - not feasible) -- You are currently subscribed to [email protected] as: [email protected] To unsubscribe, change settings or access archives, see http://www.ja-sig.org/wiki/display/JSG/cas-user -- You are currently subscribed to [email protected] as: [email protected] To unsubscribe, change settings or access archives, see http://www.ja-sig.org/wiki/display/JSG/cas-user
