In my case, the solution amounted to setting a custom property on the XA datasource
property: nonTransactionalDataSource value: true
this seems counter-intuitive, since I'm specifically trying to perform transactions with this datasource...
I have my project configured to the point where I can comment/uncomment sections in 2 files to swap back and forth
between Hibernate and OpenJPA as the persistence provider. This setting was not required for Hibernate, but it does not
seem to negatively affect the Hibernate configuration.
Joined: Mar 15, 2011
Please note that the environment for the previous posted solution
was different from the originally posed problem.
My environment is:
WAS 220.127.116.11 + JPA 2.0 FeaturePak
OpenJPA 2.0 (snapshot version which comes with the feature pak)
Also swapped the same application to use Hibernate 3.5-FINAL
Using container-managed transactions
Hopefully the same will work for the WAS 6, JPA 1.0 environment