Ondra Chaloupka created JBTM-2970:
-------------------------------------
Summary: Investigate on transaction SPI usage and if necessary for WFLY
integration
Key: JBTM-2970
URL:
https://issues.jboss.org/browse/JBTM-2970
Project: JBoss Transaction Manager
Issue Type: Task
Components: Application Server Integration, SPI
Affects Versions: 5.7.1.Final
Reporter: Ondra Chaloupka
Assignee: Ondra Chaloupka
Attachments: eap6-txn-dependencies.jpg, eap71-txn-dependencies.jpg
The transaction integration code in WFLY is pretty complicated. With the introduction of
WildFly transaction client come one more layer of abstraction and especially it should be
rethought what is the reason for using SPI there.
More than half a classes in SPI are deprecated. It would be good to understand if they are
necessary or if some refactoring would be beneficial.
As an ilustration attaching a graphic of transaction dependencies in WildFly 11.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)