[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:
-----------------------------------
From a sizing point of view, it appears that the following EMF data is
duplicated in a clustered environment (I think). The savings will be based from not
serializing the following EMF instance variables:
private final SessionFactory sessionFactory; // only UUID + name is serialized
private final PersistenceUnitTransactionType transactionType;
private final boolean discardOnClose;
private final Class sessionInterceptorClass;
private final CriteriaBuilderImpl criteriaBuilder;
private final Metamodel metamodel;
private final HibernatePersistenceUnitUtil util;
private final Map<String,Object> properties;
private final PersistenceUtilHelper.MetadataCache cache = new
PersistenceUtilHelper.MetadataCache();
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
Fix For: 4.0.0.next
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