Thanks for your help guys. I've never really considered modifying a .war outside of the normal build process an acceptable thing to do. But, it appears that is the recommended approach from the Tomcat community so I'll work with my middleware organization to see if we can get something like that to work. Obviously applying the patch to the project source and rebuilding the source is the optimal solution, however, I'm not sure how much faith I have in our build system to be able to produce builds on demand of an application years after it has gone into maintenance mode.
I still think the general idea of being able to "patch" an application without modifying the war is a useful approach in a number of situations but I see that it would not be very easy to implement/rationalize it into the platform. Thanks again for everyones help. Mike -- View this message in context: http://old.nabble.com/Classloader-between-Web-application-and-system-loader-tp27154908p27183997.html Sent from the Tomcat - User mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
