[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)

[ http://opensource.atlassian.com/projects/hibernate/browse/HHH-6727?page=c... ] Scott Marlow commented on HHH-6727: ----------------------------------- Looking at in class EntityManagerFactoryImpl, a SessionFactory (SessionFactoryImpl) instance is referenced. When the SessionFactoryImpl is serialized, only the UUID + JNDI name of SF (if configured) is serialized. The cache and other heavy instance variables are not serialized. :) The puzzling part of this for me is what happens currently in a clustered environment, where the same application SF on different machines, would have different UUIDs (and possibly no JNDI name for the SF). We must be requiring the SF JNDI name to be set, to cover that case. That would seem to be a good workaround. I look forward to seeing the clustering of the extended persistence context (EntityManager) in action, so we can go by facts, not just Scott's review of current code. ;) -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira