hi! First of all, thank you for coming up with the idea & implementing OGM. For quite some time I was thinking of using JPA annotations / semantics to drive different NoSQL stores but the whole idea of re-implementing the JPA machinery was really scary. Now we don't need to do this anymore as we've got OGM :-)
For the few past days I was looking at the org.hibernate.ogm.dialect.GridDialect interface (as well as at the existing Map, Infinispan and Ehcache implementations) and it looks like it is very easy to implement non-transactional behavior (I mean - persistence of tuples and associations is really straightforward). What I was struggling with thought is making a NoSQL store aware of the JTA-transaction demarcation. What I would like to achieve is to start a transaction in the underlying store (on transaction begin) and commit/roll it back inside data store when the JTA transaction is committed / rolled-back. Looking at the existing implementations it wasn't easy to figure out how to achieve this. Moreover I've bumped into this discussion: http://www.mail-archive.com/hibernate-dev@lists.jboss.org/msg07373.html where Emmanuel provided his insight: "Form this discussion it also seems that we might need to have datastores and dialect implement the Hibernate transaction object so that the datastore can properly demarcate when isolation starts and when it ends. But that's clearly not abstracted yet in Hibernate OGM." In the end my question is rather simple (although answer might be not...): what would be OGM-way to start / commit a transaction in the underlying data store in response to JTA transaction events? Or am I asking totaly wrong question and I should be taking a different approach? Would be grateful for any insight. Cheers, Pawel Kozlowski _______________________________________________ hibernate-dev mailing list hibernate-dev@lists.jboss.org https://lists.jboss.org/mailman/listinfo/hibernate-dev
