[jboss-svn-commits] JBL Code SVN: r22869 - in labs/jbosstm/trunk/ArjunaJTS/trailmap/docs: includes and 1 other directory.
jboss-svn-commits at lists.jboss.org
jboss-svn-commits at lists.jboss.org
Thu Sep 18 06:14:21 EDT 2008
Author: jhalliday
Date: 2008-09-18 06:14:20 -0400 (Thu, 18 Sep 2008)
New Revision: 22869
Modified:
labs/jbosstm/trunk/ArjunaJTS/trailmap/docs/DTP.xml
labs/jbosstm/trunk/ArjunaJTS/trailmap/docs/JBossTS_Configuration.xml
labs/jbosstm/trunk/ArjunaJTS/trailmap/docs/includes/trailmap_additional.xml
labs/jbosstm/trunk/ArjunaJTS/trailmap/docs/index.xml
labs/jbosstm/trunk/ArjunaJTS/trailmap/docs/part1.xml
labs/jbosstm/trunk/ArjunaJTS/trailmap/docs/part2.xml
labs/jbosstm/trunk/ArjunaJTS/trailmap/docs/part5.xml
labs/jbosstm/trunk/ArjunaJTS/trailmap/docs/part5_jta.xml
labs/jbosstm/trunk/ArjunaJTS/trailmap/docs/part5_testing_jts.xml
labs/jbosstm/trunk/ArjunaJTS/trailmap/docs/part5_testing_jtsDistributed.xml
labs/jbosstm/trunk/ArjunaJTS/trailmap/docs/part5_testing_jtsLocal.xml
labs/jbosstm/trunk/ArjunaJTS/trailmap/docs/part6.xml
labs/jbosstm/trunk/ArjunaJTS/trailmap/docs/part6_jdbc_banking.xml
labs/jbosstm/trunk/ArjunaJTS/trailmap/docs/part6_jdbc_introduction.xml
labs/jbosstm/trunk/ArjunaJTS/trailmap/docs/part6_txoj_banking_deploy.xml
labs/jbosstm/trunk/ArjunaJTS/trailmap/docs/part7.xml
Log:
Updated trail map for 4.4. JBTM-383.
Modified: labs/jbosstm/trunk/ArjunaJTS/trailmap/docs/DTP.xml
===================================================================
--- labs/jbosstm/trunk/ArjunaJTS/trailmap/docs/DTP.xml 2008-09-18 08:52:36 UTC (rev 22868)
+++ labs/jbosstm/trunk/ArjunaJTS/trailmap/docs/DTP.xml 2008-09-18 10:14:20 UTC (rev 22869)
@@ -342,7 +342,7 @@
Transaction Service</a> and finally
</li>
<li>
- The Java Community Process leaded by Sun with its <a class="linkscoloured" href="jta_overview.html">
+ The Java Community Process leaded by Sun with its <a class="linkscoloured" href="JTA_overview.html">
JTA/JTS specification</a>
</li>
</ul>
Modified: labs/jbosstm/trunk/ArjunaJTS/trailmap/docs/JBossTS_Configuration.xml
===================================================================
--- labs/jbosstm/trunk/ArjunaJTS/trailmap/docs/JBossTS_Configuration.xml 2008-09-18 08:52:36 UTC (rev 22868)
+++ labs/jbosstm/trunk/ArjunaJTS/trailmap/docs/JBossTS_Configuration.xml 2008-09-18 10:14:20 UTC (rev 22869)
@@ -33,7 +33,7 @@
</links>
<links include="includes/trailmap_additional.xml"/>
</navigation>
- <area title="Configuring the Arjuna Transaction Service">
+ <area title="Configuring the JBoss Transaction Service">
<html>
<p>This trail provides information on the way to configure environmental variables
needed to define the behaviour of transactional applications managed with JBossTS.
@@ -42,7 +42,7 @@
arguments, it is more convenient to organise and initialise them through properties
files. </p>
<h4>Properties File</h4>
-<p> The properties file named <font face="Courier New, Courier, mono">arjunajts-properties.xml
+<p> The properties file named <font face="Courier New, Courier, mono">jbossjts-properties.xml
</font> and located under the <font face="Courier New, Courier, mono"><ats_installation_directory>/etc</font>
directory is organised as a collection of property names. </p>
<blockquote>
@@ -56,10 +56,8 @@
<p>Some properties must be specified by the developer while others do not need
to be defined and can be used with their default values. Basically the properties
- file that does not provide default values to all its properties is the arjuna-properties.xml.
- Indeed, the most important properties that must be provided are the licences
- needed to execute JBossTS. </p>
- <p>The following table describes some properties in the arjuna-properties.xml, where:</p>
+ file that does not provide default values to all its properties is the jbossjts-properties.xml.</p>
+ <p>The following table describes some properties in the jbossjts-properties.xml, where:</p>
<ul>
<li>
<b>Name</b> : indicates the name of the property</li>
@@ -72,11 +70,7 @@
<strong>Value</strong>: shows the default value, if any,
assigned to the property</li>
</ul>
- <p>
- <b>
- <i>Note</i>
- </b>: In the first table ATL means Arjuna Technologies Ltd.
-</p>
+
<table BORDER="" WIDTH="100%">
<tr ALIGN="CENTER" VALIGN="CENTER" BGCOLOR="#8BD5FC">
<td width="38%">
@@ -131,7 +125,7 @@
the object store assuming it is an exclusive resource.
<p> The location of the ObjectStore is specified in via the properrty <font face="Courier New,Courier">com.arjuna.ats.arjuna.objectstore.objectStoreDir</font>
that can be passed with the java flag "-D". For convenience this property
- is defined in the properties file arjuna-properties.xml, and its value is set
+ is defined in the properties file jbossjts-properties.xml, and its value is set
during the JBossTS installation. At any time, the location of the ObjectStore
may be changed.</p>
<h4>Configuring Output</h4>
@@ -167,7 +161,7 @@
<p>According to these variables the Common Logging Framework defines three interfaces.
A particular product may implement its own classes according to its own finer
granularity. JBossTS uses the default Debugging level and the default Visibility
- level provided by CLF, but it defines its own Facility Code. ArjunaJTS uses
+ level provided by CLF, but it defines its own Facility Code. JBossTS uses
the default level assigned to its commonLoggers objects (DEBUG). However, it
uses the finer debugging features to disable or enable debug messages. Finer
values used by the JBossTS are defined below:
Modified: labs/jbosstm/trunk/ArjunaJTS/trailmap/docs/includes/trailmap_additional.xml
===================================================================
--- labs/jbosstm/trunk/ArjunaJTS/trailmap/docs/includes/trailmap_additional.xml 2008-09-18 08:52:36 UTC (rev 22868)
+++ labs/jbosstm/trunk/ArjunaJTS/trailmap/docs/includes/trailmap_additional.xml 2008-09-18 10:14:20 UTC (rev 22869)
@@ -24,7 +24,7 @@
<link ref="DTP.html">Distributed Transaction Processing</link>
<link ref="xopen_overview.html">The X/Open DTP Model</link>
<link ref="ots_overview.html">The OMG OTS Model</link>
- <link ref="jta_overview.html">Transactions in Java EE</link>
+ <link ref="JTA_Overview.html">Transactions in Java EE</link>
<link ref="JBossTS_Configuration.html">Configuring JBossTS</link>
<link ref="JBossTS_Recovery.html">
Configuring the Recovery Manager
Modified: labs/jbosstm/trunk/ArjunaJTS/trailmap/docs/index.xml
===================================================================
--- labs/jbosstm/trunk/ArjunaJTS/trailmap/docs/index.xml 2008-09-18 08:52:36 UTC (rev 22868)
+++ labs/jbosstm/trunk/ArjunaJTS/trailmap/docs/index.xml 2008-09-18 10:14:20 UTC (rev 22869)
@@ -17,7 +17,7 @@
MA 02110-1301, USA.
- (C) 2005-2006,
+ (C) 2005-2008,
@author JBoss Inc.
-->
<page title="JBossTS Trail map: Introduction" rootpath="../..">
@@ -40,7 +40,7 @@
Java EE and EJB frameworks.</p>
<p>JBossTS is a 100% Java implementation of a
<a class="linkscoloured" href="DTP.html">distributed transaction management system</a>
- based on the Sun Microsystems Java EE Java Transaction Service (<a class="linkscoloured" href="jta_overview.html">JTS</a>) standard.
+ based on the Sun Microsystems Java EE Java Transaction Service (<a class="linkscoloured" href="JTA_Overview.html">JTS</a>) standard.
Our implementation of the JTS utilizes the Object Management Group's (OMG) Object
Transaction Service (<a class="linkscoloured" href="ots_overview.html">OTS</a>) model for transaction interoperability as recommended
in the Java EE and EJB standards. Although any JTS-compliant product will allow
@@ -56,9 +56,8 @@
<p>In addition to providing full compliance with the latest version of the JTS
specification, JBossTS leads the market in providing many advanced features such
as fully distributed transactions and ORB portability with POA support.</p>
- <p>JBossTS is supported on HP-UX 11i, Linux RedHat, Microsoft Windows NT 4.0,
- Microsoft Windows 2000, Microsoft Window XP, Sun Solaris 8 operating environments
- and with any JDK 1.3 compliant environment.</p>
+ <p>JBossTS is tested on HP-UX 11i, Red Hat Linux, Windows Server 2003,
+ and Sun Solaris 10, using Sun's JDK 5. It should howerver work on any system with JDK 5 or 6.</p>
<p>The Java Transaction API support for JBossTS comes in two flavours:</p>
<ul>
<li>a purely local implementation, that does not require an ORB, but obviously
@@ -67,10 +66,10 @@
</ul>
<h4>Key features</h4>
<ul>
- <li>full compliant with the JTA 1.0.1 specification:
+ <li>full compliant with the JTA 1.1 specification:
<ul>
<li>Purely local (ORB-less) JTA offers the fastest JTA performance </li>
- <li>JDBC 2.0 support </li>
+ <li>JDBC support </li>
<li>XA compliance </li>
<li>JDBC drivers for database access with full transaction support </li>
<li>Automatic crash recovery for XAResources </li>
@@ -105,7 +104,7 @@
</p>
<p>
- This trail map will help you get started with running Arjuna transaction service product.
+ This trail map will help you get started with running JBoss transaction service product.
It is structured as follows:</p>
<ul>
<li>
Modified: labs/jbosstm/trunk/ArjunaJTS/trailmap/docs/part1.xml
===================================================================
--- labs/jbosstm/trunk/ArjunaJTS/trailmap/docs/part1.xml 2008-09-18 08:52:36 UTC (rev 22868)
+++ labs/jbosstm/trunk/ArjunaJTS/trailmap/docs/part1.xml 2008-09-18 10:14:20 UTC (rev 22869)
@@ -17,7 +17,7 @@
MA 02110-1301, USA.
- (C) 2005-2006,
+ (C) 2005-2008,
@author JBoss Inc.
-->
<page title="JBossTS Trail map: Installation Content" rootpath="../..">
@@ -37,10 +37,7 @@
<area title="Installation Content">
<html>
<h4>Verifying Installation</h4>
-By default, JBossTS is installed in the directory <font face="Courier New,Courier">/opt/jboss/jbossts</font>
-on Unix machines, and <font face="Courier New,Courier">C:\Program Files\Arjuna\ats-4.0</font>
-on Windows, except if a different location has been specified during JBossTS
-installation. When installed, the JBossTS should have the following structure.
+When installed, the binary release of JBossTS, JTS version, should have the following structure.
<ul>
<li>
<font face="Courier New,Courier">/bin</font>: this directory contains commands
@@ -49,7 +46,7 @@
<li>
<font face="Courier New,Courier">/docs</font>: this directory contains
documentation on the way to installing, administering and programming ArjunaCore,
- ArjunaTA and JBossTS.</li>
+ JBossTS JTA and JBossTS JTS.</li>
<li> <font face="Courier New,Courier">/etc</font>: this directory contains appropriate
properties files that can be used to configure the behaviour of the JBoss Transaction Service.</li>
<li>
@@ -99,7 +96,7 @@
the directory <font face="Courier New, Courier, mono"><jbossts_install_root>/trail_map/lib</font>
</li>
<li>Add the generated jar file to the CLASSPATH environment variable.</li>
- <li>Ensure that the jacorb (version 2.2.2) jar files are added in your CLASSPATH. <br/>
+ <li>Ensure that the jacorb is added in your CLASSPATH. Use only the patched version that ships with JBossTS. <br/>
<b>Ensure that JBossTS jar files appear before jacorb jar files. </b></li>
</ul>
<ul>
@@ -134,7 +131,7 @@
The JBoss Transaction Service has been designed to be highly configurable at runtime through the use of various
property attributes. Although these attributes can be provided at runtime on the
command line, it is possible (and may be more convenient) to specify them through the
-properties file <font face="Courier New,Courier">arjunajts-properties.xml</font> located under the <font face="Courier New,Courier">/etc</font> directory of the JBossTS distribution.
+properties file <font face="Courier New,Courier">jbossjts-properties.xml</font> located under the <font face="Courier New,Courier">/etc</font> directory of the JBossTS distribution.
<p>More details on the way to configure the behavior of JBossTS can be found <a class="linkscoloured" href="JBossTS_Configuration.html">here</a>.
</p>
Modified: labs/jbosstm/trunk/ArjunaJTS/trailmap/docs/part2.xml
===================================================================
--- labs/jbosstm/trunk/ArjunaJTS/trailmap/docs/part2.xml 2008-09-18 08:52:36 UTC (rev 22868)
+++ labs/jbosstm/trunk/ArjunaJTS/trailmap/docs/part2.xml 2008-09-18 10:14:20 UTC (rev 22869)
@@ -592,7 +592,7 @@
The Java Community Process leaded by Sun with
its
<a class="linkscoloured"
- href="jta_overview.html">
+ href="JTA_Overview.html">
JTA/JTS specification
</a>
</li>
Modified: labs/jbosstm/trunk/ArjunaJTS/trailmap/docs/part5.xml
===================================================================
--- labs/jbosstm/trunk/ArjunaJTS/trailmap/docs/part5.xml 2008-09-18 08:52:36 UTC (rev 22868)
+++ labs/jbosstm/trunk/ArjunaJTS/trailmap/docs/part5.xml 2008-09-18 10:14:20 UTC (rev 22869)
@@ -60,7 +60,7 @@
</li>
<li>
The PATH and CLASSPATH environment variables
- need to be set appropriately to use Arjuna
+ need to be set appropriately to use JBoss
Transaction Service. To make this easier, we
provide a shell script setup_env.sh (and for
Windows a batch file setup_env.bat) in the
@@ -102,7 +102,7 @@
<p>
<h5>Local transaction with JTA</h5>
To configure JBossTS for such transaction, edit the
- arjunajts-properties.xml file and set the following
+ jbossjts-properties.xml file and set the following
properties to the appropriate values:
<pre>
Modified: labs/jbosstm/trunk/ArjunaJTS/trailmap/docs/part5_jta.xml
===================================================================
--- labs/jbosstm/trunk/ArjunaJTS/trailmap/docs/part5_jta.xml 2008-09-18 08:52:36 UTC (rev 22868)
+++ labs/jbosstm/trunk/ArjunaJTS/trailmap/docs/part5_jta.xml 2008-09-18 10:14:20 UTC (rev 22869)
@@ -72,7 +72,7 @@
try
{
- //the following instruction asks a specific ArjunaTA
+ //the following instruction asks a specific JBossTS
//class to obtain a UserTransaction instance
<strong>javax.transaction.UserTransaction userTran =
com.arjuna.ats.jta.UserTransaction.userTransaction()</strong>;
Modified: labs/jbosstm/trunk/ArjunaJTS/trailmap/docs/part5_testing_jts.xml
===================================================================
--- labs/jbosstm/trunk/ArjunaJTS/trailmap/docs/part5_testing_jts.xml 2008-09-18 08:52:36 UTC (rev 22868)
+++ labs/jbosstm/trunk/ArjunaJTS/trailmap/docs/part5_testing_jts.xml 2008-09-18 10:14:20 UTC (rev 22869)
@@ -17,7 +17,7 @@
MA 02110-1301, USA.
- (C) 2005-2006,
+ (C) 2005-2008,
@author JBoss Inc.
-->
<page title="JBossTS Trail map: Running and Testing Examples" rootpath="../..">
@@ -36,11 +36,7 @@
<html>
<p>The JTS version of the Banking application means that the Object Request Broker
- will be used. The JBossTS distribution is provided to works with JacORB version
- 2.1 that can be obtained from the arjuna product page. JBossTS works also
- with Orbix 2000 v2.0, for more details see the ORB configuration section of the
- <a class="linkscoloured" href="../../docs/user_guide/ProgrammersGuide.pdf" target="_blank">Programmers Guide (pdf)</a>
- </p>
+ will be used. The JBossTS distribution is provided to work with the bundled JacORB version</p>
<p>To describe the possibilities provided by JBossTS to build a transactional
application according to the programming models defined by the OTS specification,
the Banking Application is programmed in different ways. </p>
Modified: labs/jbosstm/trunk/ArjunaJTS/trailmap/docs/part5_testing_jtsDistributed.xml
===================================================================
--- labs/jbosstm/trunk/ArjunaJTS/trailmap/docs/part5_testing_jtsDistributed.xml 2008-09-18 08:52:36 UTC (rev 22868)
+++ labs/jbosstm/trunk/ArjunaJTS/trailmap/docs/part5_testing_jtsDistributed.xml 2008-09-18 10:14:20 UTC (rev 22869)
@@ -17,7 +17,7 @@
MA 02110-1301, USA.
- (C) 2005-2006,
+ (C) 2005-2008,
@author JBoss Inc.
-->
<page title="JBossTS Trail map: Running and Testing Examples" rootpath="../..">
@@ -35,8 +35,7 @@
<area title="Running The Banking application with JTS">
<html>
<p>The JTS version of the Banking application means that the Object Request Broker
- will be used. The JBossTS distribution is provided to works with JacOrb version
- 2.1 that can be obtained from the same download location as JBossTS.</p>
+ will be used. The JBossTS distribution is provided to work with the bundled JacORB version</p>
<p>
<strong>Note</strong>: Ensure that the jacorb jar files are added in your CLASSPATH</p>
<ul>
@@ -153,7 +152,7 @@
managers are co-located with each application process to improve performance
and improve application fault-tolerance. When running applications which require
a separate transaction manager, you must set the com.arjuna.ats.jts.transactionManager
- property variable, in the arjunajts-properties.xml file, to YES. </p>
+ property variable, in the jbossjts-properties.xml file, to YES. </p>
<p>In a separate window, the stand-alone Transaction Server is launched as follow:</p>
<blockquote>
<font face="Courier New, Courier, mono">java com.arjuna.ats.jts.TransactionServer [-test]</font>
@@ -195,7 +194,7 @@
<li>Share the transaction service IOR on <font face="Courier New, Courier, mono">host1</font> with <font face="Courier New, Courier, mono">host2</font></li>
<p>
Open a command prompt on <font face="Courier New, Courier, mono">host2</font> and copy the <font face="Courier New, Courier, mono">CosServices.cfg</font> file
- from the <font face="Courier New, Courier, mono"><arjunajts_install_root>/etc</font> directory on <font face="Courier New, Courier, mono">host1</font>.</p>
+ from the <font face="Courier New, Courier, mono"><jbossjts_install_root>/etc</font> directory on <font face="Courier New, Courier, mono">host1</font>.</p>
<p>
For example, using the popular <font face="Courier New, Courier, mono">scp</font> package, open a shell prompt and issue the following command:</p>
<blockquote>
Modified: labs/jbosstm/trunk/ArjunaJTS/trailmap/docs/part5_testing_jtsLocal.xml
===================================================================
--- labs/jbosstm/trunk/ArjunaJTS/trailmap/docs/part5_testing_jtsLocal.xml 2008-09-18 08:52:36 UTC (rev 22868)
+++ labs/jbosstm/trunk/ArjunaJTS/trailmap/docs/part5_testing_jtsLocal.xml 2008-09-18 10:14:20 UTC (rev 22869)
@@ -17,7 +17,7 @@
MA 02110-1301, USA.
- (C) 2005-2006,
+ (C) 2005-2008,
@author JBoss Inc.
-->
<page title="JBossTS Trail map: Running and Testing Examples" rootpath="../..">
@@ -35,8 +35,7 @@
<area title="Running The Banking application with JTS">
<html>
<p>The JTS version of the Banking application means that the Object Request Broker
- will be used. The JBossTS distribution is provided to works with JacOrb version
- 2.1 that can be obtained from the same download location as JBossTS.</p>
+ will be used. The JBossTS distribution is provided to work with the bundled JacORB version</p>
<p>
<strong>Note</strong>: Ensure that the jacorb jar files are added in your CLASSPATH</p>
@@ -133,7 +132,7 @@
managers are co-located with each application process to improve performance
and improve application fault-tolerance. When running applications which require
a separate transaction manager, you must set the com.arjuna.ats.jts.transactionManager
- property variable, in the "(ats_install_dir)/etc/arjunajts-properties.xml file, to YES. </p>
+ property variable, in the "(jbossts_install_dir)/etc/jbossjts-properties.xml file, to YES. </p>
<p>In a separate window, the stand-alone Transaction Server is launched as follow:</p>
<blockquote>
<pre>java com.arjuna.ats.jts.TransactionServer [-test]</pre>
Modified: labs/jbosstm/trunk/ArjunaJTS/trailmap/docs/part6.xml
===================================================================
--- labs/jbosstm/trunk/ArjunaJTS/trailmap/docs/part6.xml 2008-09-18 08:52:36 UTC (rev 22868)
+++ labs/jbosstm/trunk/ArjunaJTS/trailmap/docs/part6.xml 2008-09-18 10:14:20 UTC (rev 22869)
@@ -80,7 +80,7 @@
<a class="linkscoloured"
href="part6_jdbc_introduction.html">
Developing applications with JDBC
- and ArjunaTA
+ and JBossTS
</a>
</li>
<li>
Modified: labs/jbosstm/trunk/ArjunaJTS/trailmap/docs/part6_jdbc_banking.xml
===================================================================
--- labs/jbosstm/trunk/ArjunaJTS/trailmap/docs/part6_jdbc_banking.xml 2008-09-18 08:52:36 UTC (rev 22868)
+++ labs/jbosstm/trunk/ArjunaJTS/trailmap/docs/part6_jdbc_banking.xml 2008-09-18 10:14:20 UTC (rev 22869)
@@ -211,7 +211,7 @@
</pre>
<h4>Note</h4>
<p>Although, this version of the banking application creates JTA local transactions,
- the way to manipulate JDBC API and the associated ArjunaTA mechanisms in the
+ the way to manipulate JDBC API and the associated JBossTS mechanisms in the
case of distributed transactions is the same.</p>
</html>
</area>
Modified: labs/jbosstm/trunk/ArjunaJTS/trailmap/docs/part6_jdbc_introduction.xml
===================================================================
--- labs/jbosstm/trunk/ArjunaJTS/trailmap/docs/part6_jdbc_introduction.xml 2008-09-18 08:52:36 UTC (rev 22868)
+++ labs/jbosstm/trunk/ArjunaJTS/trailmap/docs/part6_jdbc_introduction.xml 2008-09-18 10:14:20 UTC (rev 22869)
@@ -33,14 +33,14 @@
</links>
<links include="includes/trailmap_additional.xml"/>
</navigation>
- <area title="Developing applications with JDBC and ArjunaJTS">
+ <area title="Developing applications with JDBC and JBossTS JTS">
<html>
- <p>ArjunaJTS supports the construction of both local and distributed transactional
+ <p>JBossTS JTS supports the construction of both local and distributed transactional
applications which access databases using the JDBC APIs. JDBC supports
two-phase commit of transactions, and is similar to the XA X/Open standard.
The JDBC support is found in the com.arjuna.ats.jdbc package.</p>
<h4>Transactional Driver</h4>
- <p>The ArjunaJTS approach to incorporating JDBC connections within transactions
+ <p>The JBossTS JTS approach to incorporating JDBC connections within transactions
is to provide transactional JDBC drivers through which all interactions occur.
These drivers intercept all invocations and ensure that they are registered
with, and driven by, appropriate transactions. There is a single type of transactional
@@ -87,13 +87,13 @@
<p>From its version 2.0, the JDBC API has introduced a new way to obtain instances
of the Connection class. This is the case of the interfaces DataSource and XADataSource
- that creates transactional connections. When using a JDBC 2.0 driver, ArjunaTA
+ that creates transactional connections. When using a JDBC 2.0 driver, JBossTS
will use the appropriate DataSource whenever a connection to the database is
made. It will then obtain XAResources and register them with the transaction
via the JTA interfaces. It is these XAResources which the transaction service
will use when the transaction terminates in order to drive the database to either
commit or rollback the changes made via the JDBC connection.</p>
- <p> There are two ways in which the ArjunaTA JDBC 2.0 support can obtain XADataSources.
+ <p> There are two ways in which the JBossTS JDBC 2.0 support can obtain XADataSources.
These will be explained in the following sections. Note, for simplicity we shall
assume that the JDBC 2.0 driver is instantiated directly by the application.</p>
<ol>
@@ -129,12 +129,12 @@
<p> Many JDBC implementations provide proprietary implementations of XADataSources
that provide non-standard extensions to the specification. In order to allow
the application to remain isolated from the actual JDBC 2.0 implementation
- it is using and yet continue to be able to use these extensions, ArjunaTA
+ it is using and yet continue to be able to use these extensions, JBossTS
hides the details of these proprietary implementations using dynamic class
instantiation. In addition, the use of JNDI is not required when using this
mechanism because the actual implementation of the XADataSource will be
directly instantiated, albeit in a manner which will not tie an application
- or driver to a specific implementation. ArjunaTA therefore has several classes
+ or driver to a specific implementation. JBossTS therefore has several classes
which are for specific JDBC implementations, and these can be selected
at runtime by the application setting the dynamicClass property appropriately:
</p>
@@ -200,24 +200,24 @@
</ul>
<h4> Using the Connection</h4>
<p>Once the connection has been established (for example, using the java.sql.DriverManager.getConnection
- method), all operations on the connection will be monitored by ArjunaTA. Once
+ method), all operations on the connection will be monitored by JBossTS. Once
created, the driver and any connection can be used in the same way as any other
JDBC driver or connection.</p>
- <p> ArjunaTA connections can be used within multiple different transactions simultaneously,
+ <p> JBossTS connections can be used within multiple different transactions simultaneously,
i.e., different threads, with different notions of the current transaction,
- may use the same JDBC connection. ArjunaTA does connection pooling for each
+ may use the same JDBC connection. JBossTS does connection pooling for each
transaction within the JDBC connection. So, although multiple threads may use
the same instance of the JDBC connection, internally this may be using a different
connection instance per transaction. With the exception of close, all operations
performed on the connection at the application level will only be performed
on this transaction-specific connection.</p>
- <p> ArjunaTA will automatically register the JDBC driver connection with the transaction
+ <p> JBossTS will automatically register the JDBC driver connection with the transaction
via an appropriate resource . When the transaction terminates, this resource
will be responsible for either committing or rolling back any changes made to
the underlying database via appropriate calls on the JDBC driver.</p>
<h4>Further reading</h4>
<p>More details on the way to manage applications using the JDBC API can be found
- in the ArjunaTA Programming Guide.</p>
+ in the JBossTS Programming Guide.</p>
</html>
</area>
</content>
Modified: labs/jbosstm/trunk/ArjunaJTS/trailmap/docs/part6_txoj_banking_deploy.xml
===================================================================
--- labs/jbosstm/trunk/ArjunaJTS/trailmap/docs/part6_txoj_banking_deploy.xml 2008-09-18 08:52:36 UTC (rev 22868)
+++ labs/jbosstm/trunk/ArjunaJTS/trailmap/docs/part6_txoj_banking_deploy.xml 2008-09-18 10:14:20 UTC (rev 22869)
@@ -43,8 +43,7 @@
<h4>Distributed Configuration </h4>
<p>The banking application with Transactional Object for Java (TXOJ) is configured
to use JTS interfaces as the API to create the transaction, then an ORB to deploy
- it. The JBossTS distribution is provided to works with JacOrb version 2.1
- that can be obtained from the same download location as JBossTS.</p>
+ it. The JBossTS distribution is provided to work with the bundled JacORB version</p>
<p>
<strong>Note</strong>: Ensure that the jacorb jar files are added in your CLASSPATH</p>
<h4>Delpoy the Application</h4>
Modified: labs/jbosstm/trunk/ArjunaJTS/trailmap/docs/part7.xml
===================================================================
--- labs/jbosstm/trunk/ArjunaJTS/trailmap/docs/part7.xml 2008-09-18 08:52:36 UTC (rev 22868)
+++ labs/jbosstm/trunk/ArjunaJTS/trailmap/docs/part7.xml 2008-09-18 10:14:20 UTC (rev 22869)
@@ -66,7 +66,7 @@
<a class="linkscoloured" href="JBossTS_Recovery.html">here</a>.</i></p>
<h4>Windows</h4>
<p>
- To run the Recovery Manager as a Windows NT service, simply:</p>
+ To run the Recovery Manager as a Windows service, simply:</p>
<ol>
<li>Open a command prompt</li>
<li>cd to the directory <font face="Courier New, Courier, mono"><jbossts_install_root>\services\bin\windows</font></li>
@@ -83,7 +83,7 @@
</ol>
<h4>UNIX</h4>
<p>
- To launch the Recovery Manager on a UNIX platform, simply:</p>
+ To launch the Recovery Manager on a Linux/UNIX platform, simply:</p>
<ol>
<li>Open a command prompt</li>
<li>cd to the directory <font face="Courier New, Courier, mono"><jbossts_install_root>\services\bin\[platform]</font></li>
@@ -96,11 +96,11 @@
<area title="The Recovery Process and XAResources">
<html>
<p>
- The Arjuna recovery manager provides support for recovering XAResources whether or not they are Serializable. XAResources that <i>do</i>
+ The JBossTS recovery manager provides support for recovering XAResources whether or not they are Serializable. XAResources that <i>do</i>
implement the Serializable interface are handled without requiring additional programmer defined classes. For those XAResources that need
to recover but which cannot implement Serializable, it is possible to provide a small class which is used to help recover them.</p>
<p>
- This example shows the Arjuna recovery manager recovering a Serializable XAResource and a non-Serializable XAResource.</p>
+ This example shows the JBossTS recovery manager recovering a Serializable XAResource and a non-Serializable XAResource.</p>
<h4>The demo's components</h4>
The application consists of four classes. Each class is well documented and it is recommended that the provided code is inspected to gain
useful insight into some of the nuances of the recovery process.
@@ -112,37 +112,37 @@
<a class="linkscoloured" href="../src/com/arjuna/demo/recovery/xaresource/ExampleXAResource.java">ExampleXAResource.java</a></li>
<li>Programmer-defined support of the non-Serializable XAResource is required both in the XAResource implementation class
<a class="linkscoloured" href="../src/com/arjuna/demo/recovery/xaresource/NonSerializableExampleXAResource.java">NonSerializableExampleXAResource</a>,
- and in a class that implements a helper for the Arjuna recovery process
+ and in a class that implements a helper for the JBossTS recovery process
<a class="linkscoloured" href="../src/com/arjuna/demo/recovery/xaresource/NonSerializableExampleXAResourceRecovery.java">NonSerializableExampleXAResourceRecovery.java</a></li>
</ul>
<h4>XAResourceRecovery registration</h4>
<p>
- When recovering from failures, Arjuna requires the ability to reconnect to the XAResource
+ When recovering from failures, JBossTS requires the ability to reconnect to the XAResource
that were in use prior to the failures in order to resolve any outstanding transactions.
In order to recreate those connections for non-Serializable XAResources it is necessary to
- provide implementations of the following Arjuna interface com.arjuna.ats.jta.waitForRecovery.XAResourceRecovery.</p>
+ provide implementations of the following JBossTS interface com.arjuna.ats.jta.waitForRecovery.XAResourceRecovery.</p>
<p>
To inform the waitForRecovery system about each of the XAResourceRecovery instances, it is
- necessary to specify their class names through property variables in the arjunajts-properties.xml file.
+ necessary to specify their class names through property variables in the jbossjts-properties.xml file.
Any property variable which starts with the name XAResourceRecovery will be assumed to represent
one of these instances, and its value should be the class name.</p>
<p>
- When running XA waitForRecovery it is necessary to tell Arjuna which types of
- Xid it can recover. Each Xid that Arjuna creates has a unique node
- identifier encoded within it and Arjuna will only recover transactions
+ When running XA waitForRecovery it is necessary to tell JBossTS which types of
+ Xid it can recover. Each Xid that JBossTS creates has a unique node
+ identifier encoded within it and JBossTS will only recover transactions
and states that match a specified node identifier. The node identifier to
- use should be provided to Arjuna via a property that starts with the
+ use should be provided to JBossTS via a property that starts with the
name com.arjuna.ats.jta.xaRecoveryNode (multiple values may
- be provided). A value of * will force Arjuna to recover (and possibly
+ be provided). A value of * will force JBossTS to recover (and possibly
rollback) all transactions irrespective of their node identifier and should be
used with caution.</p>
<p>
The recovery module for the non-Serializable XAResource must be deployed in order to provide support to recover the non-Serializable XAResource.
- If this step was missed out the Serializable XAResource would recover OK but Arjuna would have no knowledge of the non-Serializable XAResource
- and so it could not recover it. To register the non-Serializable XAResource XAResourceRecovery module, add an entry to the arjunajts-properties.xml.</p>
+ If this step was missed out the Serializable XAResource would recover OK but JBossTS would have no knowledge of the non-Serializable XAResource
+ and so it could not recover it. To register the non-Serializable XAResource XAResourceRecovery module, add an entry to the jbossjts-properties.xml.</p>
<p>
Under the element <font face="Courier New, Courier, mono"><properties depends="jts" name="jta"></font>, add:</p>
@@ -155,7 +155,7 @@
<p>
By default, the recovery manager is configured to perform a pass over resources to be recovered every two minutes. It will then wait for ten seconds
before re-checking the resources. Although the test will run OK with this configuration, it is possible to configure the recovery
- manager scan times to reduce the time waiting. To configure the intervals, edit the arjunajts-properties.xml as follows:</p>
+ manager scan times to reduce the time waiting. To configure the intervals, edit the jbossjts-properties.xml as follows:</p>
<ul>
<li>Edit the property <font face="Courier New, Courier, mono">"com.arjuna.ats.arjuna.recovery.periodicRecoveryPeriod"</font>
to change the value from 120 to 5.</li>
@@ -167,17 +167,17 @@
<p>
The recovery manager will work in the same manner for either the JTA or JTS implementation. By default the JBoss Transaction Service
is configured to use a JTS transaction manager, in order to configure it to use a JTA transaction manager a change must again be made
- to the arjunajts-properties.xml. <i>See <a class="linkscoloured" href="part5_testing_jta.html">here</a> for more information on how to configure
+ to the jbossjts-properties.xml. <i>See <a class="linkscoloured" href="part5_testing_jta.html">here</a> for more information on how to configure
the JBossTS transaction manager to use JTA rather than JTS.</i></p>
<p>
<b>If you do change the transaction manager type remember to reconfigure the recovery manager as follows:</b></p>
<p>
- If you are using the ArjunaCore (raw JTA) transaction manager implementation comment out the element in arjunajts-properties.xml containing the following text:</p>
+ If you are using the ArjunaCore (raw JTA) transaction manager implementation comment out the element in jbossjts-properties.xml containing the following text:</p>
<blockquote>
<font face="Courier New, Courier, mono">internal.jta.recovery.jts.XARecoveryModule</font>
</blockquote>
<p>
- If you are using the JTS transaction manager implementation comment out the element in arjunajts-properties.xml containing the following text:</p>
+ If you are using the JTS transaction manager implementation comment out the element in jbossjts-properties.xml containing the following text:</p>
<blockquote>
<font face="Courier New, Courier, mono">internal.jta.recovery.arjunacore.XARecoveryModule</font>
</blockquote>
@@ -241,7 +241,7 @@
<h4>Recovery Module registration</h4>
The recovery module should now be deployed in order to be called by the Recovery Manager. To do so,
- we just need to add an entry in the arjunajts-properties.xml by adding a new property as follow:
+ we just need to add an entry in the jbossjts-properties.xml by adding a new property as follow:
<blockquote>
<property name="com.arjuna.ats.arjuna.recovery.recoveryExtension<i>"
value="com.arjuna.demo.recoverymodule.SimpleRecoveryModule"/>
More information about the jboss-svn-commits
mailing list