xerces.jar while migrating to 5.1.2

[Joel Kris]

While migrating from WAS4.X to WAS5.1.2 i have a problem with xerces.jar.
Since I should use xerces.jar,
I have included it in the WEB-INF/lib and packed the ear file.

Now will it create any version incompatibility while deploying it in WAS5.1.2,since in WAS5.1.2 these jars comes as default in xml.jar

[Brian Stelzer]

That is correct JDK 1.3( included with WAS V5.1.x ) includes its own version of xerces.jar.

You should be fine if you modify the classloader settings to pick up your Application xerces classes.

In WAS V4.x the default setting of the classloader was essentially PARENT_LAST, and in V5.1.x the default setting is PARENT_FIRST. So if you don't change the V5.1.x from PARENT_FIRST to PARENT_LAST the xerces classes from the JDK will get picked up instead of your Application's xercese classes. It it recommended that you change this setting at the Application level.

[Brian Stelzer]

Correction to my last post, WAS V5.1.x included JDK 1.4

[Joel Kris]

Is this applicable to jconn2.jar while migrating?
Since the ear has jconn2.jar and my server has jconn2.jar
So how should I set the class loading
Should I change

[Lin Feng]

Open your admin console
go to Servers > Application Servers > server_name
Change the Application Classloading Mode to PARENT_LAST

Thanks

Lin

[Benny Thomas]

I guess you should put your old jar files as a shared library in WAS 5.1
[ October 10, 2005: Message edited by: Benny Thomas ]