Attachment 833117 Details for Bug 1038585 – Developer guide

Developer guide

tx_dev.txt (text/plain), 1.55 KB, created by Radim Vansa on 2013-12-05 12:24:38 UTC

(hide)

Description:

Filename:

MIME Type:

Creator: Radim Vansa

Created: 2013-12-05 12:24:38 UTC

Size: 1.55 KB

patch

obsolete

>14.1. About Java Transaction API Transactions
>Red Hat JBoss Data Grid supports configuring, use of and participation in JTA compliant transactions. 
>JBoss Data Grid does the following for each cache operation:
>
>    First, it retrieves the transactions currently associated with the thread.
>    If not already done, it registers XAResource with the transaction manager to receive notifications when a transaction is committed or rolled back. 
>
>14.2. Transactions Spanning Multiple Cache Instances
>Each cache operates as a separate, standalone Java Transaction API (JTA) resource. However, components can be internally shared by Red Hat JBoss Data Grid for optimization, but this sharing does not affect how caches interact with a Java Transaction API (JTA) Manager.
>
>14.3. The Transaction Manager
>
>Use the following to obtain the TransactionManager from the cache:
>
>TransactionManager tm = cache.getAdvancedCache().getTransactionManager();
>
>To execute a sequence of operations within transaction, wrap these with calls to methods begin() and commit() or rollback() on the TransactionManager:
>
>tm.begin();
>Object value = cache.get("A");
>cache.remove("A");
>Object prev = cache.put("B", value);
>if (prev == null)
>    tm.commit();
>else
>    tm.rollback();
>
>Note:
>If a cache method returns a CacheException (or a subclass of the CacheException) within the scope of a JTA transaction, the transaction is automatically marked to be rolled back.
>
>To obtain a reference to a Red Hat JBoss Data Grid XAResource, use the following API:
>
>XAResource xar = cache.getAdvancedCache().getXAResource();
>
>

Actions: View

Attachments on bug 1038585: 833116 | 833117