[hibernate-issues] [Hibernate-JIRA] Commented: (HHH-6727) serializing an EntityManager should include enough information to later be unserialized with re-association to existing EntityManagerFactory (even on a different machine/jvm process)

[Scott Marlow (JIRA)]

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

Scott Marlow commented on HHH-6727:
-----------------------------------

One requirement for implementation, could be that a (globally) unique property is passed into the EMF when its created.  If the application is deployed in multiple JVM processes, the same property will still be passed in.  The same property can be referenced by each EntityManager to allow easy re-association with the EMF.

Another suggestion would be that if the property isn't passed in, that a UUID by used.  

SessionFactory & SessionFactoryObjectFactory classes already handle this (via JNDI name that SF should be bound to or UUID)

> serializing an EntityManager should include enough information to later be unserialized with re-association to existing EntityManagerFactory (even on a different machine/jvm process)
> --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: HHH-6727
>                 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-6727
>             Project: Hibernate Core
>          Issue Type: New Feature
>          Components: entity-manager
>            Reporter: Scott Marlow
>
> The re-association (of EM to EMF) is important, as applications expect that closing the EntityManagerFactory, will close the EntityManager's that have been opened from the EMF.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira