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

Mark Struberg (JIRA) jira-events at lists.jboss.org
Tue Sep 18 08:34:35 EDT 2012

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

Mark Struberg commented on CDI-162:

I agree on the CDI problems and I state that this is even broken in EJB. Yes, I know the old answer that EJB container vendors might implement this as Serializable. But what about the users? How can a user ever implement a portable feature based on this non-reliable functionality? 

IF the JPA entities used are only using optimistic locking and have a way to transport id+version+state info _then_ it would be possible to auto-reattach via a Serializable EM. But that is beyond the business of this very JSR.
> 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

More information about the cdi-dev mailing list