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 jars or classes will cause a problem if they contain static fields. Am I correct in this? Are there other problems that typically occur when attempting to share classes? What should I watch out for when trying to share functionality between my web apps? Thanks.
- Best practices for shared classloader use? Don Asper
- Re: Best practices for shared classloader use? mailingl...@j-b-s.de
- Re: Best practices for shared classloader use? Daniel Mikusa
- RE: Best practices for shared classloader us... Don Asper
- Re: Best practices for shared classloader us... Christopher Schultz
- RE: Best practices for shared classloader use? Don Asper
- Re: Best practices for shared classloader us... mailingl...@j-b-s.de
- RE: Best practices for shared classloade... Jeffrey Janner
- Re: Best practices for shared classl... Jens Breitenstein
- Re: Best practices for shared classloader us... chris derham
- Re: Best practices for shared classloade... Christopher Schultz