Using custom classloader

Hi: I want my web apps running on Tomcat 7.0.35 to use a custom classloader. The reason is that I want each web app classloader instance to do some processing to set up the classpath for the web app it belongs to. I have the following questions: 1) Is org.apache.catalina.loader.WebappClassLo

RE: Best practices for shared classloader use?

Thanks for your example and advice, Daniel. -Original Message- From: Daniel Mikusa [mailto:dmik...@gopivotal.com] Sent: Tuesday, June 04, 2013 12:45 PM To: Tomcat Users List Subject: Re: Best practices for shared classloader use? On Jun 4, 2013, at 11:36 AM, Don Asper wrote: > I

RE: Best practices for shared classloader use?

Sorry, I was not clear in my first post. I want to load the jars containing functionality that is common to my web apps using the shared classloader. I anticipate that there can be problems if different versions of the same class are on the shared classpath. I also suspect that any common jar

Best practices for shared classloader use?

I am considering using the Tomcat 7 shared classloader to reduce the memory footprint of my web apps. But, I'm afraid that loading my application jar files into a single classloader will cause lots of problems. I'm aware that the shared classpath should not specify multiple versions of the sam