Home/ Questions/Q 6648867
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-05-26T00:42:22+00:00

When starting WebSphere, I get this exception: Could not instantiate bean class [org.springframework.web.servlet.mvc.annotation.AnnotationMethodHandlerAdapter]: Constructor

  • 0

When starting WebSphere, I get this exception:

Could not instantiate bean class [org.springframework.web.servlet.mvc.annotation.AnnotationMethodHandlerAdapter]:
Constructor threw exception; nested exception is java.lang.ClassCastException:
com.ibm.xtq.xslt.jaxp.compiler.TransformerFactoryImpl incompatible with
javax.xml.transform.TransformerFactory
Caused by: java.lang.ClassCastException: com.ibm.xtq.xslt.jaxp.compiler.TransformerFactoryImpl
incompatible with javax.xml.transform.TransformerFactory
    at javax.xml.transform.TransformerFactory.newInstance(Unknown Source)
    at org.springframework.http.converter.xml.AbstractXmlHttpMessageConverter.<init>(AbstractXmlHttpMessageConverter.java:47)
    at org.springframework.http.converter.xml.SourceHttpMessageConverter.<init>(SourceHttpMessageConverter.java:45)
    at org.springframework.web.servlet.mvc.annotation.AnnotationMethodHandlerAdapter.<init>(AnnotationMethodHandlerAdapter.java:197)

This doesn’t seem have any impact on any beans in my applicationContext.xml but it’s still odd. For me, this looks as if IBM classes are leaking into my application.

How can I fix this? I already set the option “Access to internal server classes” to “Restrict”.

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    It was indeed a class-loading issue, however this cannot be solved by changing class-loader settings.

    The problem was that the xml-apis and javax.xml jars were being imported over some maven dependencies.

    Since we already set the class loader policies for the application to PARENT_LAST, the javax.xml.transform.TransformerFactory was being loaded from the WebApp-Class loader from our jar files.
    However its implementation ‘com.ibm.xtq.xslt.jaxp.compiler.TransformerFactoryImpl’ was coming from the server class loader, this one was linked to the javax.xml.transform.TransformerFactory provided by the JDK/JRE.

    Since the classes were loaded from different sources a ClassCastException was thrown.

    Removing all dependencies to xml-apis / xerces / javax.xml jars solved the problem.
    Since these APIs are now part of the JDK they no longer need to be imported.

    … and if you wonder why I know so much about this issue: I work together with Aaron. 😉

    • 0