[
https://issues.apache.org/jira/browse/DELTASPIKE-420?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14352003#comment-14352003
]
Thomas Andraschko commented on DELTASPIKE-420:
----------------------------------------------
Interceptors are now working - on class and on method level.
Josef's comment is outdated as we developed our own interceptor chain etc.
This means that @Transactional from DS, which is an interceptor, should work
fine. Don't know if javax.transactional.Transctional is an interceptor. If yes,
it should work fine, too.
Currently @Interceptors from CDI 1.1 is not supported but i will try add it for
future version.
> 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)
