[
https://issues.jboss.org/browse/WFLY-9588?page=com.atlassian.jira.plugin....
]
Ondra Chaloupka edited comment on WFLY-9588 at 11/14/18 7:20 AM:
-----------------------------------------------------------------
[~brian.stansberry] made the fixes for transaction subsystem to add capabilities. The
summary jira is
https://issues.jboss.org/browse/WFLY-11165.
The work consisted of adding capability for TransactionManager, UserTransaction and
TransactionSynchronizationRegistry (WFLY-11166) and for XAResourceRecoveryRegistry
(WFLY-11167). On top of that the module dependencies were stripped a bit by [fixes of me
|https://github.com/wildfly/wildfly/pull/11800] and [~yersan] (WFLY-5966, WFLY-11276,
WFLY-11263, WFLY-11342). With that txframework module was deprecated (WFLY-11271).
The task for the next work are:
* summary by Brian at his comment at
https://issues.jboss.org/browse/WFLY-11165?focusedCommentId=13659726#comm...
* making compensations module optional for transaction module (probably having a
compensations resource in the transactions subsystem or what Brian developed
https://github.com/bstansberry/wildfly/commit/0a5e51fe0988b72690b31456cbc..., it
needs to be considered), will be tracked at WFLY-9587
* considering making transaction module more granular (e.g. jta/jts integration modules
could be provided) which can bring possibility to provide jta and jts capabilities
separately (this is what I started to play with at
https://github.com/ochaloup/wildfly/tree/JBEAP-14212-jta-dependency-reorg...,
https://github.com/ochaloup/narayana/tree/JBEAP-14212-dependency-cleaning)
was (Author: ochaloup):
[~brian.stansberry] made the fixes for transaction subsystem to add capabilities. The
summary jira is
https://issues.jboss.org/browse/WFLY-11165.
The work consisted of adding capability for TransactionManager, UserTransaction and
TransactionSynchronizationRegistry (WFLY-11166) and for XAResourceRecoveryRegistry
(WFLY-11167). On top of that the module dependencies were stripped a bit by [fixes of me
|https://github.com/wildfly/wildfly/pull/11800] and [~yersan] (WFLY-5966, WFLY-11276,
WFLY-11263). With that txframework module was deprecated (WFLY-11271).
The task for the next work are:
* summary by Brian at his comment at
https://issues.jboss.org/browse/WFLY-11165?focusedCommentId=13659726#comm...
* making compensations module optional for transaction module (probably having a
compensations resource in the transactions subsystem or what Brian developed
https://github.com/bstansberry/wildfly/commit/0a5e51fe0988b72690b31456cbc..., it
needs to be considered), will be tracked at WFLY-9587
* considering making transaction module more granular (e.g. jta/jts integration modules
could be provided) which can bring possibility to provide jta and jts capabilities
separately (this is what I started to play with at
https://github.com/ochaloup/wildfly/tree/JBEAP-14212-jta-dependency-reorg...,
https://github.com/ochaloup/narayana/tree/JBEAP-14212-dependency-cleaning)
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)