Hi, Thanks for your response. Hibernate dao return object with new version. Version is used for optimistic locking mechanism. So we have hibernate dao -s and hibernate data model ( *.hbm.xml files). We want to avoid (if possible) completely rewrite this code. Another issue will be in our data model where we have a lot of hibernate entities with one-to-many relation represented by entities collection ( not id –s collection). Something similar like User and Posts relation: https://github.com/apache/ignite/blob/master/examples/src/main/java-lgpl/org/apache/ignite/examples/datagrid/hibernate/HibernateL2CacheExample.java
The question is also if we are trying to use apache ignite in correct way ? Maybe only correct way is to use apache ignite as L2 cache for hibernate dao –s ? Regards, Czeslaw -- View this message in context: http://apache-ignite-users.70518.x6.nabble.com/Cache-refresh-because-of-hibernate-versioning-mechanism-tp14394p15827.html Sent from the Apache Ignite Users mailing list archive at Nabble.com.
