PH01368:"saxparserfactory could not be instantiated"

Download Description

PH01368 resolves the following problem:

ERROR DESCRIPTION:
Thread context class loader exception when creating an XML parser factory:
Caused by: javax.xml.parsers.FactoryConfigurationError: Provider
javax.xml.parsers.SAXParserFactory could not be instantiated:
java.util.ServiceConfigurationError:
javax.xml.parsers.SAXParserFactory: Provider
org.apache.xerces.jaxp.SAXParserFactoryImpl not a subtype
at javax.xml.parsers.SAXParserFactory.newInstance(Unknown Source)
at com.ibm.ws.amm.scan.context.WARScannerContext.(WARScanne rContext.java:223)
at com.ibm.ws.jsf.ext.JSFInjectionClassListCollaborator.getFacesCon figClasses(JSFInjectionClassListCollaborator.java:145)
at com.ibm.ws.jsf.ext.JSFInjectionClassListCollaborator.getInjectio nClasses(JSFInjectionClassListCollaborator.java:123)
at com.ibm.ws.cdi.classic.CDIArchiveImpl.getInjectionClassList(CDIA rchiveImpl.java:213)
at com.ibm.ws.cdi.impl.weld.BeanDeploymentArchiveImpl.initializeJEE ComponentClasses(BeanDeploymentArchiveImpl.java:460)
at com.ibm.ws.cdi.impl.weld.BeanDeploymentArchiveImpl.scan(BeanDepl oymentArchiveImpl.java:382)

LOCAL FIX:
None

USERS AFFECTED:
Users of IBM WebSphere Application Server with CDI applications

PROBLEM DESCRIPTION:
WebSphere Application Server fails to instantiate class SAXParserFactory

RECOMMENDATION:
None

PROBLEM SUMMARY:
The problem occurs while processing CDI annotations, when the wrong context class loader is in use. The following exception is seen in the logs:
Caused by: javax.xml.parsers.FactoryConfigurationError:
Provider javax.xml.parsers.SAXParserFactory could not be
instantiated: java.util.ServiceConfigurationError:
javax.xml.parsers.SAXParserFactory: Provider
org.apache.xerces.jaxp.SAXParserFactoryImpl not a subtype
at javax.xml.parsers.SAXParserFactory.newInstance(Unknown Source)
at com.ibm.ws.amm.scan.context.WARScannerContext.(WARScanne rContext.java:223)
at com.ibm.ws.jsf.ext.JSFInjectionClassListCollaborator.getFacesCon figClasses(JSFInjectionClassListCollaborator.java:145)
at com.ibm.ws.jsf.ext.JSFInjectionClassListCollaborator.getInjectio nClasses(JSFInjectionClassListCollaborator.java:123)
at com.ibm.ws.cdi.classic.CDIArchiveImpl.getInjectionClassList(CDIA rchiveImpl.java:213)
at com.ibm.ws.cdi.impl.weld.BeanDeploymentArchiveImpl.initializeJEE ComponentClasses(BeanDeploymentArchiveImpl.java:460)
at com.ibm.ws.cdi.impl.weld.BeanDeploymentArchiveImpl.scan(BeanDepl oymentArchiveImpl.java:382)

PROBLEM CONCLUSION:
The code has been updated to ensure it is using the correct context class loader.

The fix for this APAR is currently targeted for inclusion in fix pack 9.0.0.10. Please refer to the Recommended Updates page for delivery information:
http://www.ibm.com/support/docview.wss?rs=180&uid=swg27004980