Bring consistency to use of TransactionSynchronizationRegistry in WildFly ------------------------------------------------------------------------- Key: WFLY-11446 URL: https://issues.jboss.org/browse/WFLY-11446 Project: WildFly Issue Type: Enhancement Components: Transactions Affects Versions: 15.0.0.Beta1 Reporter: Scott Marlow Assignee: Ondra Chaloupka Priority: Major See [https://github.com/wildfly/wildfly/pull/11784#discussion_r237172364] discussion about JNDI lookup of "java:jboss/TransactionSynchronizationRegistry" returning org.jboss.as.txn.service.internal.tsr.TransactionSynchronizationRegistryWrapper but other internal code sites (like EJB3, JPA container, JCA container) are directly using the org.wildfly.transaction.client.ContextTransactionSynchronizationRegistry. My suggestion is that we consider taking steps to eliminate some of the duplicate classes, so that the same TSR is always used. I think some discussion is needed to get there, but wanted to have this tracking jira. Somewhat related is that Hibernate ORM 5.3 now has direct references to org.wildfly.transaction.client.ContextTransactionManager + org.wildfly.transaction.client.LocalUserTransaction. Just mentioning in case its helpful to know for whomever looks at this jira.