Consider internal jaxb-impl module in more situations

• Build the attached jaxb-exclusion app (mvn clean package).
• Deploy inside EAP.
• Start the EAP defining a global System Property to the old ContextFactory defined in the impl module:

  ./standalone.sh -Djavax.xml.bind.context.factory=com.sun.xml.bind.v2.ContextFactory
  

• Access the URL http://localhost:8080/jaxb-exclusion/TestServlet
• A exception will be thrown in the log: "javax.xml.bind.JAXBException: Implementation of JAXB-API has not been found on module path or classpath."

The same happens if we define the same property in a jaxb.properties file.

Include the jaxb implementation library provided by the EAP in the application (this way the factory is in the thread context class loader). For example using a jboss-deployment-structure.xml:

<jboss-deployment-structure>
  <deployment>
    <dependencies>
      <module name="com.sun.xml.bind"/>
    </dependencies>
  </deployment>
</jboss-deployment-structure>

The impl module can also be added to all applications as a global module (instead of a j-d-s.xml for each application).