[
https://issues.apache.org/jira/browse/DELTASPIKE-420?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14109749#comment-14109749
]
Thomas Hug commented on DELTASPIKE-420:
---------------------------------------
Hmm, if you have the TX managed by the calling EJB, you can fix the issue
without patching. Try adding something like this
{code:java}
@Specializes
public class EjbManagedTransactionStrategy extends
ResourceLocalTransactionStrategy {
@Override
public Object execute(InvocationContext context) throws Exception {
return context.proceed();
}
}
{code}
(With @Specializes you don't need to enable a strategy in the beans.xml)
> Transactional repositories
> --------------------------
>
> Key: DELTASPIKE-420
> URL: https://issues.apache.org/jira/browse/DELTASPIKE-420
> Project: DeltaSpike
> Issue Type: New Feature
> Components: Data-Module
> Affects Versions: 0.5
> Reporter: Harald Wellmann
> Assignee: Thomas Hug
> Attachments: DELTASPIKE-420_spi.patch
>
>
> It's nice to get semi-automatic repositories from DeltaSpike Data, but these
> repositories would be even more fun if they were transactional, not
> necessarily by default, but at least by simple configuration.
> Possible approaches:
> 1) Add @Transactional to an abstract repository class, i.e.
> javax.transaction.Transactional in Java EE 7, or
> org.apache.deltaspike.jpa.api.transaction.Transactional otherwise.
> Currently, this does not work due to DELTASPIKE-419.
> 2) Make it easy to override the @Repository binding or the query handler, to
> add transactional behaviour.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
