[
http://opensource.atlassian.com/projects/hibernate/browse/HHH-6897?page=c...
]
Emmanuel Bernard edited comment on HHH-6897 at 12/15/11 7:48 AM:
-----------------------------------------------------------------
I've been thinking about it some more. The problem with UUID is that it won't be
shared between different nodes in a cluster.
I think we should
- support an explicit property as EMF name
- use the non qualified persistence unit name if none is provided
This scheme has the benefit of working both in cluster and non cluster modes and JBoss AS
can make it a bit more safe by refixing the PU name with the ear name.
No need for a UUID scheme that only covers the case were no name can be inferred and
serializability ought to happen in the same VM.
was (Author: emmanuel):
I've been thinking about it some more. The problem with UUID is that it won't
be shared between different nodes in a cluster.
I'd we should
- support an explicit property as EMF name
- use the non qualified persistence unit name if none is provided
This scheme has the benefit of working both in cluster and non cluster modes and JBoss AS
can make it a bit more safe by refixing the PU name with the ear name
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