[jboss-jira] [JBoss JIRA] (WFLY-9588) Investigate on splitting as transaction module to not be gathering all dependencies

[Ondra Chaloupka (Jira)]

    [ https://issues.jboss.org/browse/WFLY-9588?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13661084#comment-13661084 ] 

Ondra Chaloupka commented on WFLY-9588:
---------------------------------------

[~yersan] I consider the both should be removed. I think the `org.jboss.threads` for sure. There are not used anywhere what I can say. For the `org.jboss.ws.common` I think it could be removed as well. It's not used in the module directly and if I verified correctly it's not used in the Narayana either.

> Investigate on splitting as transaction module to not be gathering all dependencies
> -----------------------------------------------------------------------------------
>
>                 Key: WFLY-9588
>                 URL: https://issues.jboss.org/browse/WFLY-9588
>             Project: WildFly
>          Issue Type: Task
>          Components: Transactions
>    Affects Versions: 11.0.0.Final
>            Reporter: Ondra Chaloupka
>            Assignee: Ondra Chaloupka
>            Priority: Major
>         Attachments: eap71-txn-dependencies.jpg
>
>
> Current org.jboss.as.transaction module is heavy lifting and has many dependencies and lot of work competencies. E.g. org.jboss.jts module depends on that too.
> It should be investigated how to disentangle all the dependencies.
> Plus this could be beneficiary for WildFly Swarm if we are able to split the dependency chains, maybe not using one big jar in the transaction module but provide more granularity. Needs to be investigated.
> See attached image for a view of dependencies.



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