JBoss not using JAXP implementation even though classpath contains META-INF/services/... in JBoss EAP 7 / 6

Solution Verified - Updated -

Issue

  • JBoss not using JAXP implementation even though classpath contains META-INF/services/... in JBoss EAP 7 / 6
  • We have configured a JBoss Module which contains a JAXP implementation jar which has the META-INF/services/ file to tell the ServiceLoader the implementation to use, but when an application depends on the custom module, the JBoss default JAXP implementation is being used instead of the one we packaged in the custom module.

Environment

  • Red Hat JBoss Enterprise Application Platform (EAP)
    • 7.x
    • 6.x

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase of over 48,000 articles and solutions.

Current Customers and Partners

Log in for full access

Log In