Support enlist=JTA in Z2 Data Source
Currently the WorkUnit is the DS enlist container. This way there is always a TX.
Standard behavior would leave TX boundaries to JTA and hence there would be none by default and the use of UserTX or @Transactional defines TX boundaries.
Updated by Henning Blohm about 9 years ago
- Status changed from New to Rejected
Rejected, as we do not want to go down the road of providing XA capable connection pooling over arbitrary TMs.
Z2-Env built-in connection pooling only works for single-tx case, at best integrated with the single-commit-phase JTA impl over the z2 work unit.