[ https://issues.apache.org/jira/browse/DELTASPIKE-957?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Gerhard Petracek resolved DELTASPIKE-957. ----------------------------------------- Resolution: Not A Problem @john: if you don't agree with the arguments we provided (for keeping it as it is), please start a [discuss]-thread on the mailing-list (before we open this ticket again). if you think that the documentation isn't clear enough about this topic, you are very welcome to improve the documentation. > Improve how TransactionStrategies are looked up > ----------------------------------------------- > > Key: DELTASPIKE-957 > URL: https://issues.apache.org/jira/browse/DELTASPIKE-957 > Project: DeltaSpike > Issue Type: New Feature > Components: Data-Module, Documentation, JPA-Module > Affects Versions: 1.4.1 > Reporter: John D. Ament > > 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 -- This message was sent by Atlassian JIRA (v6.3.4#6332)