[
http://opensource.atlassian.com/projects/hibernate/browse/HHH-6897?page=c...
]
Scott Marlow commented on HHH-6897:
-----------------------------------
I thought more about the idea of mutating the PU name to always be fully qualified. That
would be an unexpected change for everyone that has already written applications for
Hibernate. Not all Hibernate JPA applications that deploy on AS7, are container managed
either (they can use the PersistenceProviderResolverHolder as some users/projects do).
Also, mutating the pu name to be fully qualified, would mean that references to the pu
name would have to also be fully qualified or be able to ignore the qualifying element.
As far as the error check, it would need to fail the deployment, as that is when we would
see that a EMF with the specified name already exists. That reminds me, we need to add
that error check not matter what, in case the application/container specifies a duplicate
EMF 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