deltaspike-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Gerhard Petracek (JIRA)" <>
Subject [jira] [Updated] (DELTASPIKE-185) Our @Transactional interceptor also tries to handle @PersistenceContexts
Date Mon, 04 Jun 2012 23:21:22 GMT


Gerhard Petracek updated DELTASPIKE-185:

    Priority: Minor  (was: Major)

minor because the current draft isn't reviewed, released,...
furthermore, as mentioned in the codi wiki the basic goal is a different one:
"... allows to define transactional beans or methods. ... It's a simple alternative to EJBs
(e.g. if you don't have an EJB container)." that means the issue just occurs if @Transactional
is used in the same bean as @PersistenceContext instead of using ejbs which are usually preferred
if the target server is an application server.

however, i've created DELTASPIKE-187 to support even such constellations.
> Our @Transactional interceptor also tries to handle  @PersistenceContexts
> -------------------------------------------------------------------------
>                 Key: DELTASPIKE-185
>                 URL:
>             Project: DeltaSpike
>          Issue Type: Bug
>          Components: JPA-Module
>    Affects Versions: 0.3-incubating
>            Reporter: Mark Struberg
>            Assignee: Mark Struberg
>            Priority: Minor
>             Fix For: 0.3-incubating
> Our @Transactional interceptor also tries to handle  @PersistenceContexts. But this will
crash any EE server. 
> A @PersistenceContext usually is bound to a JTA transaction and must not be controlled
manually. Doing so will cause Exeptions. Thus we should remove this feature. 
> This originally was intended for Java SE usage where a Persistence.createEntityManagerFactory().createEntityManager();
gets injected via e.g. OWBs simple resource plugin. A way to achieve the same would be to
rewrite @PersistenceContext to corresponding @Inject with a Qualifier if needed.

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:!default.jspa
For more information on JIRA, see:


View raw message