You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@deltaspike.apache.org by "Thomas Hug (JIRA)" <ji...@apache.org> on 2013/10/03 09:28:43 UTC
[jira] [Commented] (DELTASPIKE-420) Transactional repositories
[ https://issues.apache.org/jira/browse/DELTASPIKE-420?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13784886#comment-13784886 ]
Thomas Hug commented on DELTASPIKE-420:
---------------------------------------
I'd rather go for option 1 (seems anyway a useful feature to me). If option 2 then that should be some sort of SPI which can be leveraged by a separate transaction module.
> 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
> Priority: Critical
>
> 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.1#6144)