[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=44036#comment-44036 ] 

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

>From my quick visual inspection, EntityManagerFactoryImpl appears to have its own instance of SessionFactoryImpl. SessionFactoryImpl appears to have its own second level caches (query, entity).  Whether the second level caches would be shared with other instances of the same EMF, I'm not sure.  Just wanted to point out that if the cache isn't shared, we could end up double buffering entities/queries...

> 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: Bug
>          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