[ https://issues.jboss.org/browse/WFLY-10229?page=com.atlassian.jira.plugin... ] Scott Marlow edited comment on WFLY-10229 at 4/13/18 10:16 AM: --------------------------------------------------------------- Good point, for me, I didn't realize that WildFly TSR wrapper class was referencing the com.arjuna.ats.jta.TransactionManager instance directly still, which skips using the org.wildfly.transaction.client.ContextTransactionManager instance so I was thinking of that as the "why" as well, but *agreed* that is more of the "*how*". :) This is kind of dangerous that we won't know if an application is directly using com.arjuna.ats.jta.TransactionManager or org.wildfly.transaction.client.ContextTransactionManager, not that applications should directly use a TransactionManager but they might be. Is this a valid concern? was (Author: smarlow): Good point, for me, I didn't realize that WildFly TSR wrapper class was referencing the com.arjuna.ats.jta.TransactionManager instance directly still, which skips using the org.wildfly.transaction.client.ContextTransactionManager instance so I was thinking of that as the "why" as well, but *agreed* that is more of the "*how*. :) This is kind of dangerous that we won't know if an application is directly using com.arjuna.ats.jta.TransactionManager or org.wildfly.transaction.client.ContextTransactionManager, not that applications should directly use a TransactionManager but they might be. Is this a valid concern? -- This message was sent by Atlassian JIRA (v7.5.0#75005)