[jboss-svn-commits] JBL Code SVN: r36462 - labs/jbosstm/trunk/ArjunaCore/docs/ArjunaCore_Development_Guide/en-US.

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

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

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

Modified: labs/jbosstm/trunk/ArjunaCore/docs/ArjunaCore_Development_Guide/en-US/Overview.xml
===================================================================
--- labs/jbosstm/trunk/ArjunaCore/docs/ArjunaCore_Development_Guide/en-US/Overview.xml	2010-12-19 13:36:31 UTC (rev 36461)
+++ labs/jbosstm/trunk/ArjunaCore/docs/ArjunaCore_Development_Guide/en-US/Overview.xml	2010-12-19 23:49:19 UTC (rev 36462)
@@ -5,8 +5,14 @@
 ]>
 <chapter>
   <title>Overview</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>
+  <para>
     This chapter contains a description of the use of the TxCore transaction engine and the <application>Transactional
     Objects for Java (TXOJ)</application> classes and facilities. The classes mentioned in this chapter are the key to
     writing fault-tolerant applications using transactions. Thus, they are described and then applied in the
@@ -41,7 +47,8 @@
     <para>
       TxCore exploits object-oriented techniques to present programmers with a toolkit of Java classes from which
       application classes can inherit to obtain desired properties, such as persistence and concurrency control. These
-      classes form a hierarchy, part of which is shown in <xref linkend="txcore_class_hierarchy" /> and which will be described later in this document.
+      classes form a hierarchy, part of which is shown in <xref linkend="txcore_class_hierarchy" /> and which will be
+      described later in this document.
     </para>
     <figure id="txcore_class_hierarchy">
       <title>TxCore Class Hierarchy</title>
@@ -53,9 +60,9 @@
     </figure>
     <para>
       Apart from specifying the scopes of transactions, and setting appropriate locks within objects, the application
-      programmer does not have any other responsibilities: TxCore and <application>TXOJ</application> guarantee
-      that transactional objects will be registered with, and be driven by, the appropriate transactions, and crash
-      recovery mechanisms are invoked automatically in the event of failures.
+      programmer does not have any other responsibilities: TxCore and <application>TXOJ</application> guarantee that
+      transactional objects will be registered with, and be driven by, the appropriate transactions, and crash recovery
+      mechanisms are invoked automatically in the event of failures.
     </para>
   </section>