[
http://opensource.atlassian.com/projects/hibernate/browse/HHH-6897?page=c...
]
Scott Marlow edited comment on HHH-6897 at 12/19/11 10:31 AM:
--------------------------------------------------------------
At application deployment time, a warning will be generated if the EMF registry
Map<String,Set<EMF>> already contains an entry for the EMF. The warning can
be ignored for applications that don't use passivation or cluster replication of the
EM.
When the EM is deserialized, if more than one entry is in the set
(Map<String,Set<EMF>>), an error is thrown.
was (Author: smarlow(a)redhat.com):
At application deployment time, a DEBUG will be generated if the EMF registry
Map<String,Set<EMF>> already contains an entry for the EMF. The warning can
be ignored for applications that don't use passivation or cluster replication of the
EM.
When the EM is deserialized, if more than one entry is in the set
(Map<String,Set<EMF>>), an error is thrown.
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