Yes, that is the exact situation we are attempting to avoid in Tomcat. In our WSA implementation we can simply replace the effected JARS in one location and it is implemented against all WARs running in that server's context. In the illustration you provided below we would need to repackage, or at the very least, redistribute the "shared" jar files that have changes to each WAR. In our situation, we would not be distributing the WARs across running server instances...the application is self-contained and runs as a unit anyway. It's packaged software that requires customization. -- View this message in context: http://www.nabble.com/Classloader-question-t1332679.html#a3573057 Sent from the Tomcat - User forum at Nabble.com.
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
