[jboss-svn-commits] JBL Code SVN: r35702 - labs/jbosstm/trunk/ArjunaJTA/docs/ArjunaTA_Installation_And_Administration_Guide/en-US.

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

Author: misty at redhat.com
Date: 2010-10-25 01:16:05 -0400 (Mon, 25 Oct 2010)
New Revision: 35702

Modified:
   labs/jbosstm/trunk/ArjunaJTA/docs/ArjunaTA_Installation_And_Administration_Guide/en-US/Errors_And_Exceptions.xml
Log:
Fixed ugly table in Errors and Exceptions chapter

Modified: labs/jbosstm/trunk/ArjunaJTA/docs/ArjunaTA_Installation_And_Administration_Guide/en-US/Errors_And_Exceptions.xml
===================================================================
--- labs/jbosstm/trunk/ArjunaJTA/docs/ArjunaTA_Installation_And_Administration_Guide/en-US/Errors_And_Exceptions.xml	2010-10-25 04:51:28 UTC (rev 35701)
+++ labs/jbosstm/trunk/ArjunaJTA/docs/ArjunaTA_Installation_And_Administration_Guide/en-US/Errors_And_Exceptions.xml	2010-10-25 05:16:05 UTC (rev 35702)
@@ -10,52 +10,40 @@
     This section covers the types and causes of errors and exceptions which may be thrown or reported during a
     transactional application.
   </para>
-  <table>
+  <variablelist>
     <title>Errors and Exceptions</title>
-    <tgroup cols="2">
-      <colspec colnum="1" colwidth="100px" />
-      <colspec colnum="2" colwidth="340px" />
-      <thead>
-        <row>
-          <entry>Error</entry>
-          <entry>Description</entry>
-        </row>
-      </thead>
-      <tbody>
-        <row>
-          <entry><para><literal>NO_MEMORY</literal></para></entry>
-          <entry>
-            <para>
-              The application has run out of memory, and has thrown an <systemitem>OutOfMemoryError</systemitem>
-              exception. <application>ArjunaTA</application> has attempted to do some cleanup, by running the garbage
-              collector, before re-throwing the exception. This is probably a transient problem and retrying the
-              invocation should succeed.
-            </para>
-          </entry>
-        </row>
-        <row>
-          <entry><para><literal>com.arjuna.ats.arjuna.exceptions.FatalError</literal></para></entry>
-          <entry>
-            <para>
-              An error has occurred, and the error is of such severity that that the transaction system must shut
-              down. Prior to this error being thrown the transaction service ensures that all running transactions have
-              rolled back. If an application catches this error, it should tidy up and exit. If further work is
-              attempted, application consistency may be violated.
-            </para>
-          </entry>
-        </row>
-        <row>
-          <entry><para><literal>com.arjuna.ats.arjuna.exceptions.ObjectStoreError</literal></para></entry>
-          <entry>
-            <para>
-              An error occurred while the transaction service attempted to use the object store. Further forward
-              progress is not possible.
-            </para>
-          </entry>
-        </row>
-      </tbody>
-    </tgroup>
-  </table>
+    <varlistentry>
+      <term><literal>NO_MEMORY</literal></term>
+      <listitem>
+        <para>
+          The application has run out of memory, and has thrown an <systemitem>OutOfMemoryError</systemitem>
+          exception. <application>ArjunaTA</application> has attempted to do some cleanup, by running the garbage
+          collector, before re-throwing the exception. This is probably a transient problem and retrying the invocation
+          should succeed.
+        </para>
+      </listitem>
+    </varlistentry>
+    <varlistentry>
+      <term><literal>com.arjuna.ats.arjuna.exceptions.FatalError</literal></term>
+      <listitem>
+        <para>
+          An error has occurred, and the error is of such severity that that the transaction system must shut
+          down. Prior to this error being thrown the transaction service ensures that all running transactions have
+          rolled back. If an application catches this error, it should tidy up and exit. If further work is attempted,
+          application consistency may be violated.
+        </para>
+      </listitem>
+    </varlistentry>
+    <varlistentry>
+      <term><literal>com.arjuna.ats.arjuna.exceptions.ObjectStoreError</literal></term>
+      <listitem>
+        <para>
+          An error occurred while the transaction service attempted to use the object store. Further forward progress is
+          not possible.
+        </para>
+      </listitem>
+    </varlistentry>
+  </variablelist>
   <para>
     Object store warnings about access problems on states may occur during the normal execution of crash recovery. This
     is the result of multiple concurrent attempts to perform recovery on the same transaction. It can be safely ignored.