[hibernate-issues] [Hibernate-JIRA] Commented: (HHH-6897) serialization of the EntityManager should be possible
[
http://opensource.atlassian.com/projects/hibernate/browse/HHH-6897?page=c...
]
Scott Marlow commented on HHH-6897:
-----------------------------------
Yeah, I forgot to mention in my previous reply, that UUID avoids the deployment conflict,
that could happen if we defaulted to using the non qualified pu name.
For the clustered case, non-qualified pu name is not unique enough for a cluster. The
container should be able to pass in a unique EMF name.
Even with containers that know to pass in the unique EMF name, application managed entity
managers will not likely specify the unique EMF name. So, I agree that defaulting to UUID
covers more cases.
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