[
https://issues.apache.org/jira/browse/DELTASPIKE-957?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14627744#comment-14627744
]
Gerhard Petracek commented on DELTASPIKE-957:
---------------------------------------------
please try it with our global alternative feature (as documented).
the bda-rule-interpretation in weld based servers was the only reason for that
feature.
> 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)
