[
https://issues.apache.org/jira/browse/DELTASPIKE-185?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13288970#comment-13288970
]
Gerhard Petracek edited comment on DELTASPIKE-185 at 6/4/12 10:43 PM:
----------------------------------------------------------------------
+1
we have to move it to an optional approach as we did in codi - just one of few
parts we have to refactor in the current draft.
imo we don't need jira tickets for snapshot versions. we can just refactor it
(without breaking tests for important use-cases).
was (Author: gpetracek):
+1
we have to move it to an optional approach as we did in codi - just one of few
parts we have to refactor in the current draft.
> Our @Transactional interceptor also tries to handle @PersistenceContexts
> -------------------------------------------------------------------------
>
> Key: DELTASPIKE-185
> URL: https://issues.apache.org/jira/browse/DELTASPIKE-185
> Project: DeltaSpike
> Issue Type: Bug
> Components: JPA-Module
> Affects Versions: 0.3-incubating
> Reporter: Mark Struberg
> Assignee: Mark Struberg
> 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:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
