PQ69817: DIFFERENT VERSION OF XERCES IN WAR CAUSES CLASSCASTEXCEPTION FROM ORG.APACHE.XERCES.PARSERS.STANDARDPARSERCONFIGURATION

 Fixes are available

5.0.1: WebSphere Application Server Version 5.0 Fix Pack 1 (Version 5.0.1)
5.0.2: WebSphere Application Server Version 5.0 Fix Pack 2 (Version 5.0.2)
5.0.1: WebSphere Application Server Enterprise Edition Version 5.0 Fix Pack 1



APAR status
Closed as program error.

Error description
Different version of xerces in WAR  causes ClassCastException
from org.apache.xerces.parsers.StandardParserConfiguration
java.lang.ClassCastException:
org.apache.xerces.parsers.StandardParserConfiguration
at org.apache.xerces.parsers.DOMParser.<init>(DOMParser.java:109
at org.apache.xerces.jaxp.DocumentBuilderImpl.<init>(DocumentBui
at org.apache.xerces.jaxp.DocumentBuilderFactoryImpl.newDocument
at org.apache.jasper.parser.ParserUtils.parseXMLDocument(ParserU
at org.apache.jasper.compiler.TagLibraryInfoImpl.parseTLD(TagLib
at org.apache.jasper.compiler.TagLibraryInfoImpl.<init>(TagLibra
at org.apache.jasper.compiler.TagLibraryInfoImpl.<init>(TagLibra
at org.apache.jasper.compiler.ConfigurableParseEventListener.<in
at org.apache.jasper.compiler.ParserController.<init>(ParserCont
at org.apache.jasper.compiler.Compiler.compile(Compiler.java:210
org.apache.jasper.parser.ParserUtils.parseXMLDocument needs to
call com.ibm.ws.xml.ParserFactory.newDocumentBuilderFactory to
fix this problem.
Local fix Problem summary
****************************************************************
* USERS AFFECTED: All users of WebSphere Application Server    *
*                 5.0 release with applications using its      *
*                 own Parser.                                  *
****************************************************************
* PROBLEM DESCRIPTION: Different versions of Xerces in WAR     *
*                      file causes ClassCastException.         *
****************************************************************
* RECOMMENDATION:                                              *
****************************************************************
The problem is that the context classloader needs to be set to
the runtime classloader so we don't pick up the application
version of the DocumentBuilder and Document objects for the
work we are doing inside the runtime.
Problem conclusion
Added new methods to utility class com.ibm.ws.xml.ParserFactory
that runtime components (webcontainer, pagelist ...) can use to
obtain the correct DocumentBuilder and Document objects.
Temporary fix
PQ69817_eFix.jar
Comments
APAR information
APAR number PQ69817
Reported component name WAS BASE 5.0
Reported component ID 5630A3600
Reported release 00W
Status CLOSED PER
PE NoPE
HIPER NoHIPER
Special Attention NoSpecatt
Submitted date 2003-01-13
Closed date 2003-01-30
Last modified date 2003-01-30

APAR is sysrouted FROM one or more of the following:

APAR is sysrouted TO one or more of the following:

Modules/Macros
JSP          

Publications Referenced

Fix information
Fixed component name WAS BASE 5.0
Fixed component ID 5630A3600

Applicable component levels
R003 PSY    UP
R00A PSY    UP
R00H PSY    UP
R00I PSY    UP
R00S PSY    UP
R00W PSY    UP


Document Information


Product categories: Software > Application Servers > Distributed Application & Web Servers > WebSphere Application Server > General
Operating system(s):
Software version: 00W
Software edition:
Reference #: PQ69817
IBM Group: Software Group
Modified date: Jan 30, 2003