How Do I Avoid The Dom Level 1 Problem In Websphere?

1.	How Do I Avoid The Dom Level 1 Problem In Websphere?
Answer» WebSphere has the same issue with DOM Level 1 interfaces as VAJ above. The SOLUTION is to do one the following: Put the path to xerces.jar (or other DOM Level 2 interfaces) in the variable 'com.ibm.ejs.sm.adminserver.classpath' in the file admon.config. This resides in $WAS_ROOT$/bin before all other variables. Or, if you run WAS $WAS_ROOT/bin/debug/adminserver.{bat\|sh} add a line 'set WAS_CP=xerces.jar' (or other DOM Level 2 interfaces) before other set WAS_CP commands. Or, add JDOM to the application server CLASSPATH, USING either the admin.cfg file or the administration CONSOLE. WebSphere has the same issue with DOM Level 1 interfaces as VAJ above. The solution is to do one the following:

Answer»

WebSphere has the same issue with DOM Level 1 interfaces as VAJ above. The SOLUTION is to do one the following:

Put the path to xerces.jar (or other DOM Level 2 interfaces) in the variable 'com.ibm.ejs.sm.adminserver.classpath' in the file admon.config. This resides in $WAS_ROOT$/bin before all other variables.
Or, if you run WAS $WAS_ROOT/bin/debug/adminserver.{bat|sh} add a line 'set WAS_CP=xerces.jar' (or other DOM Level 2 interfaces) before other set WAS_CP commands.
Or, add JDOM to the application server CLASSPATH, USING either the admin.cfg file or the administration CONSOLE.

WebSphere has the same issue with DOM Level 1 interfaces as VAJ above. The solution is to do one the following:

Discussion