From 043599757602785266be7a8e6897fcba1eecac76 Mon Sep 17 00:00:00 2001 From: costin Date: Thu, 16 Sep 2010 14:00:28 +0300 Subject: [PATCH] SGF-21 SGF-19 + add transaction manager documentation --- docs/src/docbkx/reference/data.xml | 10 ++++++++-- 1 file changed, 8 insertions(+), 2 deletions(-) diff --git a/docs/src/docbkx/reference/data.xml b/docs/src/docbkx/reference/data.xml index 0b4db21d..1e87683e 100644 --- a/docs/src/docbkx/reference/data.xml +++ b/docs/src/docbkx/reference/data.xml @@ -79,12 +79,18 @@ transparently across multiple APIs that can be configured either programmatically or declaratively (the most popular choice). - For Gemfire, SGF provides a dedicated, per-cache, transaction + For GemFire, SGF provides a dedicated, per-cache, transaction manager that once declared, allows actions on the Regions to be grouped and executed atomically through Spring: - <bean id="transaction-manager" class="org.springframework.data.gemfire.GemfireTransactionManager" p:cache-ref="cache"/> + <gfe:transaction-manager id="tx-manager" cache-ref="cache"/> + The example above can be simplified even more by eliminating the cache-ref attribute if the GemFire cache is defined under the default + name gemfire-cache. As with the other SGF namespace elements, if the cache name is not configured, the aforementioned naming convention will used. + Additionally, the transaction manager name, if not specified is gemfire-transaction-manager. + + or if you prefer bean declarations: + <bean id="tx-manager" class="org.springframework.data.gemfire.GemfireTransactionManager" p:cache-ref="cache"/> Note that currently GemFire supports optimistic transactions with read committed isolation. Furthermore, to guarantee