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 2015/02/13 15:30:12 UTC
[jira] [Reopened] (DELTASPIKE-420) Transactional repositories
[ https://issues.apache.org/jira/browse/DELTASPIKE-420?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Gerhard Petracek reopened DELTASPIKE-420:
-----------------------------------------
Assignee: Jozef Hartinger (was: Thomas Hug)
as mentioned at DELTASPIKE-823 it works with weld, but not with wildfly.
it would be great if we can support wildfly as well.
> 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.2.2
>
> 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)