[GERONIMO-5824] jpa JTA transaction and missing jta-data-source should be warned about or rejected

• Type: Bug
• Status: Open
• Priority: Major
• Resolution: Unresolved
• Affects Version/s: 2.1.8, 2.2.2, 3.0.0
• Component/s: persistence
• Security Level: public (Regular issues)
• Assignee: Unassigned
• Reporter: David Jencks
• Created: 18/Feb/11 07:11
• Updated: 28/May/12 03:11

Description

Someone just had a lot of weird transaction errors that turned out to be because they had configured a persistence.xml with JTA transaction support and only a non-jta-datasource that was actually transactional. When both the tm and openjpa tried to control the tx confusion enused.

We can detect this situation on deployment and either reject it or at least loudly warn about it.