Websphere Application Server Extension Classloader jar conflict

Question

I have 2 WebApplications in my WAS.

1. I don't have the source code of B.
2. A .jar that B uses to run, is in the same path where the Extension Classloader jars are being loaded from.

Thus this jar is being referenced in project A and it prevents my app from running because it has conflicts with the JAR that B uses.

I can't move the .jar from there because I don't have the source code to manually set a path to load that file.

Is there a way to tell Websphere not to use a specific .jar for a specific application?

Thanks in advance.

Answer 1

Thanks for your information , i finally fixed this issue by removing te jars that where not allowing me to start, then i started all my applications(A), the applications(A) took their own jars. and then i modified the was classloader at execution time to re-use the negative jars, and i pasted them back in the problematic folder, then started (B).

It works as a patch and i dont recommend to do it. It made them work by now. But it will fail when WebSphere restars again but for now i´ll get the source code and modify, the jar dependencies, and re-install B in WAS <- Thats the correct steps in order to get transparent application server re-starts when needed.