Classloader mode in WebSphere

[meimei li]

My application need use a newer version jdom.jar under my WAR file WEB-INF/lib instead of the one under WebSphere/AppServer/lib. After I installed the war file, in the "configuration" page of this application, I changed its WAR-class loader policy to "module" and classloader mode to "PARENT_LAST", but web server still finds the wrong version.

However, if in the configuration page of the particular server, I changed the application class loading policy to "PARENT_LAST", and the application classloader mode remains "multiple", the WAR-class loader policy to "application", classloader mode remains "PARENT_LAST", it finds the correct jar file.

Anybody knows why? In my opinion, the first approach should work as well.

Thanks.

[Pradeep bhatt]

You could use the Classloader viewer for debugging purpose

http://www-106.ibm.com/developerworks/websphere/library/techarticles/0312_cocasse/0312_cocasse.html