[
https://issues.jboss.org/browse/AS7-2076?page=com.atlassian.jira.plugin.s...
]
Scott Marlow commented on AS7-2076:
-----------------------------------
When the EJB3 container passivates an extended persistence context, all of the SFSBs that
reference the extended persistence context will also need to be passivated.
I mentioned needing some SPI above for clustering. I think that the EJB3 container will
probably also need to use the SPI. I'm thinking of two method calls:
1. void serializeXPCStart()
2. SessionID[] serializeXPCFinish()
Where SessionID is from StatefulSessionComponentInstance.getId().
Note: perhaps SFSBPCMap could change to just storing the SessionID obtained from
StatefulSessionComponentInstance.getId().
activation/passivation of extended persistence context
------------------------------------------------------
Key: AS7-2076
URL:
https://issues.jboss.org/browse/AS7-2076
Project: Application Server 7
Issue Type: Task
Components: JPA / Hibernate
Affects Versions: 7.1.0.Alpha1
Reporter: Scott Marlow
Assignee: Scott Marlow
Fix For: 7.1.0.Beta1
Currently, SFSBXPCMap directly references ExtendedEntityManager. ExtendedEntityManager
implements the extended persistence context (contains a direct reference of the underlying
persistence context.
To support activation/passivation. SFSBXPCMap should instead reference the XPC via an
uuid (or something like that), that can be used to get the XPC (if SFSB is in activated
state).
Note EJB 3.1 specification section 4.2.1 titled Instance Passivation and Conversational
State:
"
A container must not passivate a stateful session bean with an extended persistence
context unless the
following conditions are met:[9]
* All the entities in the persistence context are serializable.
* The EntityManager is serializable.
[9] The container is not permitted to destroy a stateful session bean instance because it
does not meet these requirements.
"
--
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