[
https://issues.jboss.org/browse/WFLY-1001?page=com.atlassian.jira.plugin....
]
Stuart Douglas resolved WFLY-1001.
----------------------------------
Resolution: Done
The Java EE spec actually requires us to do this. For a Java EE deployment all the Java EE
API's have to be available to the deployment, no matter if the deployment uses them or
not.
jaxrs subsystem pulls in javax.xml.bind.api module for every
deployment
-----------------------------------------------------------------------
Key: WFLY-1001
URL:
https://issues.jboss.org/browse/WFLY-1001
Project: WildFly
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Class Loading, REST
Reporter: Kyle Lape
Assignee: Kyle Lape
Priority: Minor
The jaxrs subsystem automatically pulls in the JAXB API module for every single
deployment, even if they don't have a JAX-RS component in them. This is normally not
noticed since {{javax.xml.bind.api}} is already added to the deployment via
{{javaee.api}}, but you want to include your own version of JAXB in your deployment, then
you will need to exclude {{javaee.api}}, which is expected. But it's not expected to
have to exclude the jaxrs subsystem, too.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see:
http://www.atlassian.com/software/jira