You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@deltaspike.apache.org by "Gerhard Petracek (JIRA)" <ji...@apache.org> on 2014/03/03 12:26:22 UTC

[jira] [Comment Edited] (DELTASPIKE-420) Transactional repositories

    [ https://issues.apache.org/jira/browse/DELTASPIKE-420?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13917966#comment-13917966 ] 

Gerhard Petracek edited comment on DELTASPIKE-420 at 3/3/14 11:25 AM:
----------------------------------------------------------------------

suggested change (see patch)


was (Author: gpetracek):
suggested change

> 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)