[jboss-svn-commits] JBL Code SVN: r36464 - labs/jbosstm/trunk/ArjunaJTS/docs/ArjunaJTS_Development_Guide/en-US.

[jboss-svn-commits at lists.jboss.org]

Author: misty at redhat.com
Date: 2010-12-19 18:53:28 -0500 (Sun, 19 Dec 2010)
New Revision: 36464

Modified:
   labs/jbosstm/trunk/ArjunaJTS/docs/ArjunaJTS_Development_Guide/en-US/Overview.xml
Log:
Adding conceptual definition of a transaction

Modified: labs/jbosstm/trunk/ArjunaJTS/docs/ArjunaJTS_Development_Guide/en-US/Overview.xml
===================================================================
--- labs/jbosstm/trunk/ArjunaJTS/docs/ArjunaJTS_Development_Guide/en-US/Overview.xml	2010-12-19 23:51:52 UTC (rev 36463)
+++ labs/jbosstm/trunk/ArjunaJTS/docs/ArjunaJTS_Development_Guide/en-US/Overview.xml	2010-12-19 23:53:28 UTC (rev 36464)
@@ -8,6 +8,13 @@
   
   <section>
     <title>Defining a transaction</title>
+    <para>
+      A transaction is a unit of work that encapsulates multiple database actions such that that either all the
+      encapsulated actions fail or all succeed.
+    </para>
+    <para>
+      Transactions ensure data integrity when an application interacts with multiple datasources.
+    </para>
     <formalpara>
       <title>Practical Example</title>
       <para>
@@ -26,8 +33,8 @@
     </para>
     <para>
       "Transactions" in this guide refers to atomic transactions, and embody the "all-or-nothing" concept outlined
-      above. Transactions are used to guarantee the consistency of data in the presence of failures. Transactions fulfill
-      the requirements of ACID: Atomicity, Consistency, Isolation, Durability.
+      above. Transactions are used to guarantee the consistency of data in the presence of failures. Transactions
+      fulfill the requirements of ACID: Atomicity, Consistency, Isolation, Durability.
     </para>
     <variablelist>
       <title>ACID Properties</title>