[infinispan-issues] [JBoss JIRA] (ISPN-9214) JBossStandaloneJTAManagerLookup is using deprecated integration names
[
https://issues.jboss.org/browse/ISPN-9214?page=com.atlassian.jira.plugin....
]
Scott Marlow commented on ISPN-9214:
------------------------------------
Thanks [~pruivo], the JNDI name still looks correct. For the direct reference to
com.arjuna.ats.jta.TransactionManager, I'm not exactly sure of what that needs to
change to (beyond changing to use
org.wildfly.transaction.client.ContextTransactionManager#getInstance.) Does Infinispan
need to manage its own TM instance when not running inside of WF? Do you have code to
com.arjuna.ats.jta.TransactionManager setup code somewhere?
I assume that you still need your com.arjuna.ats.jta.TransactionManager setup code, but
will also now need to initialize org.wildfly.transaction.client.ContextTransactionManager
to work with the started com.arjuna.ats.jta.TransactionManager.
What do you recommend [~dmlloyd] + [~tomjenkinson] that Infinispan change in their code?
JBossStandaloneJTAManagerLookup is using deprecated integration
names
---------------------------------------------------------------------
Key: ISPN-9214
URL: https://issues.jboss.org/browse/ISPN-9214
Project: Infinispan
Issue Type: Task
Components: Core, Integration
Reporter: Sanne Grinovero
Assignee: Scott Marlow
Priority: Minor
Scott changed the Hibernate ORM {{JBossStandaloneJTAManagerLookup}}, as on WildFly 13+,
JTA client code that directly references the {{com.arjuna.ats.jta.TransactionManager}},
needs to instead use the WildFly Transaction Client, or it may see incorrect TX status.
I assume the Infinispan standalone client will need to be updated as well.
See:
- https://hibernate.atlassian.net/browse/HHH-12640
- https://hibernate.atlassian.net/browse/HHH-12620
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)