[DELTASPIKE-957] Improve how TransactionStrategies are looked up

• Type: New Feature
• Status: Closed
• Priority: Major
• Resolution: Not A Problem
• Affects Version/s: 1.4.1
• Component/s: Data-Module, Documentation, JPA-Module
• Assignee: Unassigned
• Reporter: John D. Ament
• Created: 15/Jul/15 01:08
• Updated: 19/Jul/15 13:13
• Resolved: 16/Jul/15 18:42

Description

Currently transaction strategies are implemented as alternatives. I created a WAR for WildFly 9, and ran into a lot of issues getting it to work. My WAR has many JARs in it, all with beans.xml files. I tried to enable the alternative in various spots, but no luck, even went through all 30 beans.xml files in my project and enabled it. Still went with the default transaction strategy.

In order to fix, I had to enable a global alternative with the strategy. This seems to go against our docs, which indicate it should be a regular alternative.

I'd recommend a few things to think about.

• Expect a concrete producer.
• Use a class look up in apache-deltaspike.properties