Opentaps Hibernate Integration - Revision history

Sichen: /* Unit Tests */

2010-11-05T16:42:48Z

‎Unit Tests

2009-12-01T18:48:37Z

‎Configuring Hibernate

2009-12-01T18:26:23Z

2009-11-26T11:27:09Z

‎Caching

2009-11-26T01:54:47Z

‎Caching

2009-11-26T01:51:13Z

2009-11-21T04:09:09Z

‎Caching

2009-11-21T04:00:51Z

‎Caching

2009-11-21T03:58:42Z

‎Caching

2009-11-21T03:58:03Z

‎Caching

@@ Line 262: / Line 262: @@
 Unit tests for hibernate are found in <tt>org.opentaps.tests.entity.HibernateTests</tt> in the opentaps-tests component.
 == Learning More ==
 The best way to learn more about how to use hibernate with opentaps is to look through the unit tests in <tt>org.opentaps.tests.entity.HibernateTests</tt> as an example.

← Older revision		Revision as of 18:48, 1 December 2009
Line 186:		Line 186:

	=== Configuring Hibernate ===		=== Configuring Hibernate ===
		+
		+	Currently hibernate in opentaps accesses the database through the entity engine, via the <tt>OpentapsConnectionProvider</tt> to obtain database connections and <tt>OpentapsTransactionFactory</tt>/<tt>OpentapsTransactionManagerLookup</tt> for transaction management. The connection pool, transaction manager, and maximum number of connections are all obtained from the entity engine for hibernate.

	=== Base Class Annotations ===		=== Base Class Annotations ===

@@ Line 140: / Line 140: @@
 <pre>
    <property name="hibernate.cache.provider_class">org.hibernate.cache.EhCacheProvider</property>
    <property name="hibernate.search.worker.execution">async</property>
    <property name="hibernate.cache.use_query_cache">true</property>

@@ Line 149: / Line 149: @@
 You can disable the caching feature by removing or commenting out these lines (both HibernateCfg.ftl and hibernate.cfg.xml).
-<br/><br/>
+{{note|Important|The entities of current open hibernate session will not update when they are changed by ofbiz entity engine after session has already been opened, so you must open a new session to get a refreshed version of the object. In contrast, if you update a value with hibernate, it will be refreshed in the ofbiz entity engine's cache.  This is due to the different way the ofbiz entity engine works versus hibernate -- the ofbiz delegator is a static object, whereas each hibernate session is a different object.}}
 === Using Hibernate without the OFBIZ Entity Engine ===

@@ Line 136: / Line 136: @@
 === Caching ===
-Our caching system now support ofbiz <-> hibernate mutual cache clearing. It mean it will sync hibernate cache on you update GenericValue with ofbiz entity engine, and vice versa. The hibernate cache configuration is locate in HibernateCfg.ftl (it also in hibernate.cfg.xml) as following:
 <pre>
    <property name="hibernate.search.worker.execution">async</property>
    <property name="hibernate.cache.use_query_cache">true</property>
@@ Line 144: / Line 146: @@
    <property name="hibernate.search.worker.thread_pool.size">5</property>
 </pre>
-you can disable the caching feature by remove these lines (both HibernateCfg.ftl and hibernate.cfg.xml).
 <br/><br/>
 {{note|Important|The entities of current open session will not update when it changed by ofbiz entity engine after session open, you must using open a new session to get fresh object. Creating a session is not expensive, keeping one alive a long time is maybe less expensive.}}

@@ Line 145: / Line 145: @@
 </pre>
 you can disable the caching feature by remove these lines (both HibernateCfg.ftl and hibernate.cfg.xml).
 Note: the entities of current open session will not update when it change by ofbiz entity engine, you must using open a new session to get fresh object. and the best practise is also close your session when it finish the job.