Yes, quite correct on your statement regarding using "Application" as the definition. The essence of what we are looking for is a similar behavior with Tomcat. Our over arching goal is to minimize or eliminate the need to have jars that are to be shared by more than one applicaiton (WAR) be copied into each applicaiton. We would like to have them in one place where they can be accessed by all applicaitons. We've achieved this somewhat by placing the jar in the shared jars folder. However, the delegation model prohibits instantiating classes that belong to an application from any entity in the shared jars folder.
If Tomcat does not have a similar facility as mentioned regarding WebSphere, what is considered to be the "best practices" approach as far as Tomcat is concerned? -- View this message in context: http://www.nabble.com/Classloader-question-t1332679.html#a3570566 Sent from the Tomcat - User forum at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
