I've seen that javaee6 with ejb 3.1 solves two major issues in
stateful session beans (concurrent accesss, passivation with extended
persistence context), from the ejb 3.1 specs:
1) The container serializes calls to each stateful and stateless
session bean instance. Most containers will support many instances of
a session bean executing concurrently; however, each instance sees
only a serialized sequence of method calls. Therefore, a stateful or
stateless session bean does not have to be coded as reentrant.
2) A container must not passivate a stateful session bean with an
extended persistence context unless the following conditions are met:
•All the entities in the persistence context are serializable.
•The EntityManager is serializable.
If my understanding of point 2 this means that if entities and entity
manager are serializable is a container responsibility to passivare
and reconstruct the extended persistence context.
I have only a question about the statement "The EntityManager is
serializable": does it means that it is implementation dependent? If
it is so, is the eclipselink (JPA implementation included in
glassfish) implementation of entitymanager serializable?
Best regards,
Roberto
--
You received this message because you are subscribed to the Google Groups "javaee6-codecamp" group.
To post to this group, send email to javaee6-...@googlegroups.com.
To unsubscribe from this group, send email to javaee6-codeca...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/javaee6-codecamp?hl=en.