[
https://issues.apache.org/jira/browse/DELTASPIKE-420?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14109723#comment-14109723
]
Franck Garcia commented on DELTASPIKE-420:
------------------------------------------
I'm using DS 1.0.0 with wildfly v.8.1.0.FINAL and I got the following error
when trying to use an injected Repository into a SLSB:
{code}
JBAS014237: Only session and message-driven beans with bean-managed transaction
demarcation are allowed to access UserTransaction]
{code}
I did not try the patch suggested by Harald, but having the DS Data component
not usable with EJB is really a blocker. Is it something that is plan to be
fixed in future releases?
> 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)
