WAS has a copy of XML parser (i.e. xalan.jar and xerces.jar) in its lib directory. However, my application is using a different version of xerces, so I have a different copy in my application lib/ext directory. If I set the class loader policy to PARENT_FIRST, it seems IBM's one is loaded and I got some warnings from my application. If I set the class loader policy to PARENT_LAST, it seems my xerces is loaded, then I got some warnings when WAS start the EJB container. Is there anyway I can make WAS to load its XML parser and my application to reload the parser to use my own version? Thanks
set application class loader policy to be MULTIPLE
SCJP, SCJD, SCWCD, SCBCD, SCEA, IBM Certified Enterprise Developer, WebSphere Studio V5.0
posted 15 years ago
I have already set the application class loader policy to 'MULTIPLE' and class loader module to 'PARENT_LAST'. But it does not help. I guess the solution you mention here work if the jar files are user provided. However, in this case, one xerces.jar is provided by WAS in its library path and the other is given by the user, it may make the scenario complicated.