Using standalone JTA 1.2 with Deltaspike JPA

[oranheim]

Hi,

I'm trying to use JTA-and-Hibernate (quickstart/jta-and-hibernate at master · jbosstm/quickstart · GitHub) with Apache DeltaSpike JTA (http://deltaspike.apache.org/jpa.html). I'm able to use transactions in my test-case using the TransactionManager, but I want to have DeltaSpike JPA working.

Please se line 52 and 53: https://github.com/apache/deltaspike/blob/master/deltaspike/modules/jpa/impl/src/main/java/org/apache/deltaspike/jpa/impl/transaction/BeanManagedUserTransactionStrategy.java

How can I bind TransactionSynchronizationRegistry to java:comp/TransactionSynchronizationRegistry? - mine is bound to java:/jboss/TransactionSynchronizationRegistry. Ref. line 70 in https://github.com/jbosstm/quickstart/blob/master/jta-and-hibernate/src/test/java/org/jboss/narayana/quickstarts/jta/TestCase.java.

Cheers,

Ove

[tomjenkinson]

I am just wondering, if you are using the jbosstm QS, can;t you change the binding names (just change jboss to comp on the following lines):

quickstart/jta-and-hibernate/src/test/java/org/jboss/narayana/quickstarts/jta/TestCase.java at master · jbosstm/quicksta…

quickstart/jta-and-hibernate/src/test/java/org/jboss/narayana/quickstarts/jta/TestCase.java at master · jbosstm/quicksta…

Inside WildFly itself I am not too sure how to change the binding names for the respective JEE transaction objects. This is the code that is doing the binding:

wildfly/transactions/src/main/java/org/jboss/as/txn/deployment/TransactionJndiBindingProcessor.java at master · wildfly/…

It looks to be binding to /comp rather than /jboss.

[tomjenkinson]

I'm just thinking, it is possible that you were bitten by this one: [JBTM-2054] JNDI names from JTAEnvironmentBean should be used in ArjunaJTA/cdi classes - JBoss Issue Tracker

[tomjenkinson]

Hi Ove,

How are you getting on with this, do you require any further assistance?

Thanks,

Tom

[oranheim]

Hi Tom!

Thanks for following up on me. I'm doing fine. I choose to use Spring Data CDI together with DeltaSpike JPA, because it supports JTA 1.2, which DS guys don't want at this point. They implement their own custom (portable) Transactional support.

So far so good

Cheers,

Ove