[jboss-jira] [JBoss JIRA] (AS7-3387) separation of passivation/replication operations for extended persistence context

[Scott Marlow (JIRA)]

     [ https://issues.jboss.org/browse/AS7-3387?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Scott Marlow resolved AS7-3387.
-------------------------------

         Assignee:     (was: Paul Ferraro)
    Fix Version/s:     (was: 7.1.0.Final)
       Resolution: Out of Date

    
> separation of passivation/replication operations for extended persistence context
> ---------------------------------------------------------------------------------
>
>                 Key: AS7-3387
>                 URL: https://issues.jboss.org/browse/AS7-3387
>             Project: Application Server 7
>          Issue Type: Task
>          Components: Clustering, EJB
>            Reporter: Scott Marlow
>
> Currently, when the JPA extended persistence context is serializing, it is not known if passivation or cluster replication is occurring.  This means that the extended persistence context will stay in memory.  When ExtendedEntityManager.writeObject() is invoked, I would like a way to tell that the current thread is passivating versus cluster replicating. 
> If this isn't going to happen, I'll look at alternatives.  A quick rejection or response that this makes sense, would be welcome.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira