[
https://issues.apache.org/jira/browse/DELTASPIKE-420?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14351999#comment-14351999
]
Harald Wellmann commented on DELTASPIKE-420:
--------------------------------------------
This is issue is now marked as resolved, but it is not clear how the solution
works, and I don't see any updates in the docs.
Are repositories now transactional out of the box?
Is it enough to add {{@Transactional}} at class level? If so, which annotation
to use - the one from DeltaSpike JPA, or from javax.transactional?
How to make this work on WildFly 8.2.0?
>From Jozef's comment in DELTASPIKE-823:
{quote}
A workaround would be to use @Interceptors or @Priority with CDI 1.1+
{quote}
Does that apply to DeltaSpike's {{TransctionalInterceptor}}, or to WildFly's
JTA interceptor? How to add an annotation to a framework or container class,
other than by subclassing and placing the annotation on the subclass - is that
the intended approach?
A code example would be very helpful.
> 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: Jozef Hartinger
> Fix For: 1.3.0
>
> 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.3.4#6332)
