[jboss-svn-commits] JBL Code SVN: r30442 - labs/jbosstm/enterprise/tags/EAP_4_2_8/Programmers_Guide/en-US.
jboss-svn-commits at lists.jboss.org
jboss-svn-commits at lists.jboss.org
Wed Dec 2 19:27:44 EST 2009
Author: laubai
Date: 2009-12-02 19:27:43 -0500 (Wed, 02 Dec 2009)
New Revision: 30442
Modified:
labs/jbosstm/enterprise/tags/EAP_4_2_8/Programmers_Guide/en-US/Book_Info.xml
labs/jbosstm/enterprise/tags/EAP_4_2_8/Programmers_Guide/en-US/Chapter.xml
labs/jbosstm/enterprise/tags/EAP_4_2_8/Programmers_Guide/en-US/Chapter_02.xml
labs/jbosstm/enterprise/tags/EAP_4_2_8/Programmers_Guide/en-US/Chapter_03.xml
Log:
Added changes for JBPAPP-1712.
Modified: labs/jbosstm/enterprise/tags/EAP_4_2_8/Programmers_Guide/en-US/Book_Info.xml
===================================================================
--- labs/jbosstm/enterprise/tags/EAP_4_2_8/Programmers_Guide/en-US/Book_Info.xml 2009-12-02 23:20:43 UTC (rev 30441)
+++ labs/jbosstm/enterprise/tags/EAP_4_2_8/Programmers_Guide/en-US/Book_Info.xml 2009-12-03 00:27:43 UTC (rev 30442)
@@ -8,7 +8,7 @@
<edition>2.0</edition>
<pubsnumber>1</pubsnumber>
<productname>JBoss Enterprise Application Platform</productname>
- <productnumber>4.5</productnumber>
+ <productnumber>4.2</productnumber>
<abstract>
<para>This book is the Enterprise Application Platform edition of the JBoss TS Programmers
Guide</para></abstract>
Modified: labs/jbosstm/enterprise/tags/EAP_4_2_8/Programmers_Guide/en-US/Chapter.xml
===================================================================
--- labs/jbosstm/enterprise/tags/EAP_4_2_8/Programmers_Guide/en-US/Chapter.xml 2009-12-02 23:20:43 UTC (rev 30441)
+++ labs/jbosstm/enterprise/tags/EAP_4_2_8/Programmers_Guide/en-US/Chapter.xml 2009-12-03 00:27:43 UTC (rev 30442)
@@ -21,7 +21,7 @@
<para><classname>TxCore</classname> 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 below and which will be described later in this document.</para>
- <mediaobject id="figure_1">
+ <mediaobject id="figure_1"><title>TXCore Class Heirarchy</title>
<imageobject>
<imagedata align="center" fileref="images/TXCore_class_hierarchy.png" />
</imageobject>
@@ -126,7 +126,7 @@
<para>A persistent object not in use is assumed to be held in a <emphasis>passive</emphasis> state with its state residing in an object store and <emphasis>activated</emphasis> on demand. The fundamental life cycle of a persistent object in <emphasis>TXOJ</emphasis> is shown in <xref linkend="figure_2"/>.</para>
- <mediaobject id="figure_2">
+ <mediaobject id="figure_2"><title>Persistent Object Lifecycle</title>
<imageobject>
<imagedata align="center" fileref="images/Persistent_Object_Lifecycle.png" />
</imageobject>
Modified: labs/jbosstm/enterprise/tags/EAP_4_2_8/Programmers_Guide/en-US/Chapter_02.xml
===================================================================
--- labs/jbosstm/enterprise/tags/EAP_4_2_8/Programmers_Guide/en-US/Chapter_02.xml 2009-12-02 23:20:43 UTC (rev 30441)
+++ labs/jbosstm/enterprise/tags/EAP_4_2_8/Programmers_Guide/en-US/Chapter_02.xml 2009-12-03 00:27:43 UTC (rev 30442)
@@ -275,9 +275,9 @@
<para><emphasis>TxCore</emphasis> supports two models for objects, which as we shall show affect how an objects state and concurrency control are implemented:</para>
<itemizedlist>
- <listitem><para><termdef>SINGLE</termdef>: only a single copy of the object exists within the application; this will reside within a single JVM, and all clients must address their invocations to this server. This model provides better performance, but represents a single point of failure, and in a multi-threaded environment may not protect the object from corruption if a single thread fails.</para>
+ <listitem><para><literal>SINGLE</literal>: only a single copy of the object exists within the application; this will reside within a single JVM, and all clients must address their invocations to this server. This model provides better performance, but represents a single point of failure, and in a multi-threaded environment may not protect the object from corruption if a single thread fails.</para>
- <mediaobject id="figure_3">
+ <mediaobject id="figure_3"><title>Single Object Model</title>
<imageobject>
<imagedata align="center" fileref="images/Single_Object.png" />
</imageobject>
@@ -649,4 +649,4 @@
</section>
-</chapter>
\ No newline at end of file
+</chapter>
Modified: labs/jbosstm/enterprise/tags/EAP_4_2_8/Programmers_Guide/en-US/Chapter_03.xml
===================================================================
--- labs/jbosstm/enterprise/tags/EAP_4_2_8/Programmers_Guide/en-US/Chapter_03.xml 2009-12-02 23:20:43 UTC (rev 30441)
+++ labs/jbosstm/enterprise/tags/EAP_4_2_8/Programmers_Guide/en-US/Chapter_03.xml 2009-12-03 00:27:43 UTC (rev 30442)
@@ -147,7 +147,7 @@
<para>In addition to normal top-level and nested atomic actions <emphasis>TxCore</emphasis> also supports independent top-level actions, which can be used to relax strict serialisability in a controlled manner. An independent top-level action can be executed from anywhere within another atomic action and behaves exactly like a normal top-level action, that is, its results are made permanent when it commits and will not be undone if any of the actions within which it was originally nested abort.</para>
- <mediaobject id="figure_5">
+ <mediaobject id="figure_5"><title>Independent Top-Level Action</title>
<imageobject>
<imagedata align="center" fileref="images/Independent_Top-Level.png" />
</imageobject>
More information about the jboss-svn-commits
mailing list