[cdi-dev] [JBoss JIRA] (CDI-162) Support Extended Persistence Contexts in Managed beans

Tue Sep 18 09:58:36 EDT 2012

    [ https://issues.jboss.org/browse/CDI-162?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12719477#comment-12719477 ] 

Scott Marlow commented on CDI-162:
----------------------------------

[~struberg]
All of the related issues should be discussed IMO, with regard to the discussion of supporting extended persistence contexts in managed beans ([including the issues that you raised|https://struberg.wordpress.com/2012/04/25/is-there-a-way-to-fix-the-jpa-entitymanager]).

>From a clustering/passivation point of view, EntityManager's that have joined a JTA transaction, shouldn't be replicated or passivated (see above quote from EJB3 spec "A container may only passivate a stateful session bean instance when the instance is not in a transaction.").  Without a JTA transaction, no database locks should be held.  Obviously, there is more to your comment than I am understanding (otherwise you wouldn't of said that there is a problem.  Even though I'm not yet understanding the locking issue, I still think that applications will be written to avoid problems that could occur (at least they will want to).

> Support Extended Persistence Contexts in Managed beans
> ------------------------------------------------------
>
>                 Key: CDI-162
>                 URL: https://issues.jboss.org/browse/CDI-162
>             Project: CDI Specification Issues
>          Issue Type: Tracker
>    Affects Versions: 1.0
>            Reporter: Pete Muir
>             Fix For: 1.1 (Proposed)
>
>

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira