[
http://opensource.atlassian.com/projects/hibernate/browse/HHH-6897?page=c...
]
Scott Marlow commented on HHH-6897:
-----------------------------------
I'm wrong in my [second to last
comment|https://hibernate.onjira.com/browse/HHH-6897?focusedCommentId=446...]
above.
Its not a deployment error, for the EMF name to be shared. The EMF name is only used
during deserialization. which would be for cluster replication or session bean
passivation followed by activation.
The simple case, of non-clustered and not using session bean passivation/activation is
find with Hibernate defaulting to the pu name. For passivation/activation/replication
other containers need to set the "hibernate.entitymanager_factory_name" property
to a unique value. That is the same everywhere that application is deployed.
serialization of the EntityManager should be possible
-----------------------------------------------------
Key: HHH-6897
URL:
http://opensource.atlassian.com/projects/hibernate/browse/HHH-6897
Project: Hibernate Core
Issue Type: Task
Affects Versions: 4.0.0.CR7
Reporter: Scott Marlow
Assignee: Scott Marlow
Fix For: 4.0.1
http://pastie.org/3018508 contains the NotSerializableException:
org.hibernate.service.internal.StandardServiceRegistryImpl exception and
http://pastie.org/3018879 describes some of contained values that don't appear to be
serializable.
I would like to see this fixed in either 4.0.0.Final or a 4.0.1.Final (if that could
happen in time). I'll have more information soon, regarding fix version.
--
This message is automatically generated by JIRA.
For more information on JIRA, see:
http://www.atlassian.com/software/jira