[hibernate-issues] [Hibernate-JIRA] Commented: (HHH-6897) serialization of the EntityManager should be possible

Scott Marlow (JIRA) noreply at atlassian.com
Thu Dec 15 09:03:19 EST 2011


    [ http://opensource.atlassian.com/projects/hibernate/browse/HHH-6897?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=44596#comment-44596 ] 

Scott Marlow commented on HHH-6897:
-----------------------------------

Agreed that the UUID won't work on a cluster.  However, if someone deploys a bunch of applications on some other container, and several of the applications use the same persistence unit name.  At deserialization time, we could have issues but more likely, the applications won't deploy because of the non qualified pu name conflict (if we threw an error from the PersistenceProvider.createContainerEntityManagerFactory()).

The applications could code around that of course or they could deploy to a container that passes the explicit property for 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

        


More information about the hibernate-issues mailing list