[jboss-jira] [JBoss JIRA] (WFLY-11195) Module dependency on org.jboss.as.xts from org.jboss.xts should be optional.

[James Perkins (Jira)]

     [ https://issues.jboss.org/browse/WFLY-11195?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

James Perkins updated WFLY-11195:
---------------------------------
    Fix Version/s: 15.0.0.Final


> Module dependency on org.jboss.as.xts from org.jboss.xts should be optional.
> ----------------------------------------------------------------------------
>
>                 Key: WFLY-11195
>                 URL: https://issues.jboss.org/browse/WFLY-11195
>             Project: WildFly
>          Issue Type: Enhancement
>          Components: XTS
>            Reporter: Brian Stansberry
>            Assignee: Brian Stansberry
>            Priority: Major
>             Fix For: 15.0.0.Beta1, 15.0.0.Final
>
>
> The org.jboss.xts module depends on org.jboss.as.xts.  It does so to allow the WildflyTransactionClientTxBridgeIntegrationHandler class to be found after the XTS subsystem's XTSHandlerDeploymentProcessor wires its name into the deployment.
> But if there is no xts subsystem, then there's no XTSHandlerDeploymentProcessor and thus there's no wiring of the class name nor any need to load the class.
> So, this dependency is optional and should be marked as such.
> The reason this is important is that we currently have this dependency chain:
> org.jboss.as.transactions/org.jboss.narayana.compensations/org.jboss.xts/org.jboss.as.xts/org.jboss.as.webservices.server.integration 
> And org.jboss.as.transactions is used from quite a lot of places. And that means this org.jboss.xts dependency brings the whole WS stack into a lot of places.  Making this link optional will allow Galleon to optimize that away.



--
This message was sent by Atlassian Jira
(v7.12.1#712002)