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

Ondra Chaloupka (JIRA) issues at jboss.org
Mon Dec 4 04:20:00 EST 2017


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

Ondra Chaloupka edited comment on WFLY-9588 at 12/4/17 4:19 AM:
----------------------------------------------------------------

not sure if directly block WFLY-9455 but making easier more granular dependency graph could help a lot in solving it


was (Author: ochaloup):
not sure if directly block WFLY-9455 but making easier more granular dependency graph could help a lot in solving it

> 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
>         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.5.0#75005)


More information about the jboss-jira mailing list