JBoss 6.1.0 - java.lang.ClassCastException: com.ctc.wstx.stax.WstxInputFactory cannot be cast to jav

[Maciej Opala]

Hi,

When I deploy in JBoss 6.1.0 my web application packed in an ear archive I obtain the following error in logs:

java.lang.ClassCastException: com.ctc.wstx.stax.WstxInputFactory cannot be cast to javax.xml.stream.XMLInputFactory
java.lang.ClassCastException: com.ctc.wstx.stax.WstxInputFactory cannot be cast to javax.xml.stream.XMLInputFactory

I do some xml processing just after the context of application gets initialized. I guess that this error has something in common with the content of WEB-INF/lib directory of the ear which is:

avalon-framework-4.1.3.jar
commons-codec-1.4.jar
commons-collections-3.2.1.jar
commons-io-2.0.jar
commons-lang3-3.0.jar
commons-logging-1.1.jar
commons-transaction-1.2.jar
dom4j-1.6.1.jar
drools-commons-1.0.jar
geronimo-stax-api_1.0_spec-1.0.jar
log4j-1.2.16.jar
logkit-1.0.1.jar
poi-3.7.jar
poi-ooxml-3.7.jar
poi-ooxml-schemas-3.7.jar
servlet-api-2.3.jar
simulator-commons-1.0.jar
stax-api-1.0.1.jar
xml-apis-1.0.b2.jar
xmlbeans-2.3.0.jar

I was trying removing both stax-api-1.0.1.jar and geronimo-stax-api_1.0_spec-1.0.jar but then new exception occurred:

Caused by: java.lang.LinkageError: loader constraint violation: when resolving method "javax.xml.stream.XMLInputFactory.createXMLStreamReader(Ljavax/xml/transform/Source;)Ljavax/xml/stream/XMLStreamReader;" the class loader (instance of org/jboss/classloader/spi/base/BaseClassLoader) of the current class, com/in4mates/commons/xml/XMLUtils, and the class loader (instance of <bootloader>) for resolved class, javax/xml/stream/XMLInputFactory, have different Class objects for the type javax/xml/transform/Source used in the signature

Really no idea what to do. Any help would be greatly appreciated..

[Peter Johnson]

Also remove the servlet-api.jar file, you don't need that, JBoss AS provides it. Hopefully that will fix the error.

[Maciej Opala]

I've removed the following libs:

xml-apis
stax
geronimo

which solved the problem finally. It seems strange because same war with mentioned libs was deployed well on JBoss 4.2.3GA. Any explanation? I agree with servlet api, will also remove it.

[Peter Johnson]

Most likely, JBoss AS 6 is already providing that functionality found in those JARs, whereas 4.2.3 didn't.