[jboss-svn-commits] JBL Code SVN: r6396 - in labs/jbosstm/trunk: ArjunaCore/arjuna/classes/com/arjuna/ats/arjuna/coordinator ArjunaCore/arjuna/classes/com/arjuna/ats/internal/arjuna/objectstore ArjunaCore/arjuna/etc ArjunaCore/arjuna/services/config ArjunaCore/arjuna/services/scripts/unix ArjunaCore/docs/install_guide ArjunaCore/docs/user_guide ArjunaCore/scripts ArjunaCore/tsmx/etc ArjunaCore/tsmx/etc/jmxbrowser ArjunaCore/tsmx/etc/objectstorebrowser ArjunaCore/tsmx/etc/perfgraph ArjunaJTA/docs/install_guide ArjunaJTA/docs/user_guide ArjunaJTS/docs/release_notes ArjunaJTS/docs/user_guide ArjunaJTS/jts/classes/com/arjuna/ats/internal/jts ArjunaJTS/jts/classes/com/arjuna/ats/internal/jts/interposition ArjunaJTS/jts/classes/com/arjuna/ats/internal/jts/interposition/resources/arjuna ArjunaJTS/jts/classes/com/arjuna/ats/internal/jts/interposition/resources/restricted ArjunaJTS/jts/classes/com/arjuna/ats/internal/jts/orbspecific ArjunaJTS/jts/classes/com/arjuna/ats/internal/jts/orbspecific! /coordinator ArjunaJTS/jts/classes/com/arjuna/ats/internal/jts/recovery/contact ArjunaJTS/jts/classes/com/arjuna/ats/jts ArjunaJTS/jts/classes/com/arjuna/ats/jts/extensions ArjunaJTS/jts/classes/com/arjuna/ats/jts/utils ArjunaJTS/jts/services/config ArjunaJTS/jts/services/scripts/unix ArjunaJTS/orbportability/docs/programmers_guide ArjunaJTS/trailmap ArjunaJTS/trailmap/docs ArjunaJTS/trailmap/docs/includes ArjunaJTS/trailmap/src/com/arjuna/demo/jta/jdbcbank ArjunaJTS/trailmap/src/com/arjuna/demo/jta/localbank ArjunaJTS/trailmap/src/com/arjuna/demo/jts/explicitremotebank ArjunaJTS/trailmap/src/com/arjuna/demo/jts/localbank ArjunaJTS/trailmap/src/com/arjuna/demo/jts/remotebank ArjunaJTS/trailmap/src/com/arjuna/demo/jts/txojbank ArjunaJTS/trailmap/src/com/arjuna/demo/recovery/xaresource ArjunaJTS/trailmap/src/com/arjuna/demo/recoverymodule ArjunaJTS/trailmap/src/com/arjuna/demo/simple atsintegration/docbuild/docs atsintegration/scripts common/classes/com/arjuna/common/internal! /util/logging ext
jboss-svn-commits at lists.jboss.org
jboss-svn-commits at lists.jboss.org
Sun Sep 24 03:18:36 EDT 2006
Author: mark.little at jboss.com
Date: 2006-09-24 03:16:18 -0400 (Sun, 24 Sep 2006)
New Revision: 6396
Added:
labs/jbosstm/trunk/ArjunaJTS/orbportability/docs/programmers_guide/ProgrammersGuide.doc
labs/jbosstm/trunk/ArjunaJTS/trailmap/docs/JBossTS_Configuration.xml
labs/jbosstm/trunk/ArjunaJTS/trailmap/docs/JBossTS_ORBPortability.xml
labs/jbosstm/trunk/ArjunaJTS/trailmap/docs/JBossTS_Recovery.xml
Removed:
labs/jbosstm/trunk/ArjunaJTS/orbportability/docs/programmers_guide/ORB Portability Layer - Programmers Guide.doc
labs/jbosstm/trunk/ArjunaJTS/trailmap/docs/ArjunaTS_Configuration.xml
labs/jbosstm/trunk/ArjunaJTS/trailmap/docs/ArjunaTS_ORBPortability.xml
labs/jbosstm/trunk/ArjunaJTS/trailmap/docs/ArjunaTS_Recovery.xml
Modified:
labs/jbosstm/trunk/ArjunaCore/arjuna/classes/com/arjuna/ats/arjuna/coordinator/TxStats.java
labs/jbosstm/trunk/ArjunaCore/arjuna/classes/com/arjuna/ats/internal/arjuna/objectstore/JDBCActionStore.java
labs/jbosstm/trunk/ArjunaCore/arjuna/classes/com/arjuna/ats/internal/arjuna/objectstore/JDBCStore.java
labs/jbosstm/trunk/ArjunaCore/arjuna/etc/default-CommonLogging-properties.xml
labs/jbosstm/trunk/ArjunaCore/arjuna/services/config/recoveryservice.conf
labs/jbosstm/trunk/ArjunaCore/arjuna/services/scripts/unix/recoverymanagerservice.sh
labs/jbosstm/trunk/ArjunaCore/docs/install_guide/InstallGuide.doc
labs/jbosstm/trunk/ArjunaCore/docs/user_guide/FailureRecoveryGuide.doc
labs/jbosstm/trunk/ArjunaCore/docs/user_guide/ProgrammersGuide.doc
labs/jbosstm/trunk/ArjunaCore/scripts/run-tools.bat
labs/jbosstm/trunk/ArjunaCore/scripts/run-tools.sh
labs/jbosstm/trunk/ArjunaCore/scripts/setup-env.bat
labs/jbosstm/trunk/ArjunaCore/scripts/setup-env.sh
labs/jbosstm/trunk/ArjunaCore/scripts/start-recovery-manager.sh
labs/jbosstm/trunk/ArjunaCore/scripts/start-transaction-service.sh
labs/jbosstm/trunk/ArjunaCore/tsmx/etc/jmxbrowser/tools.properties
labs/jbosstm/trunk/ArjunaCore/tsmx/etc/objectstorebrowser/tools.properties
labs/jbosstm/trunk/ArjunaCore/tsmx/etc/perfgraph/tools.properties
labs/jbosstm/trunk/ArjunaCore/tsmx/etc/toolsframework.xml
labs/jbosstm/trunk/ArjunaJTA/docs/install_guide/InstallGuide.doc
labs/jbosstm/trunk/ArjunaJTA/docs/user_guide/ProgrammersGuide.doc
labs/jbosstm/trunk/ArjunaJTS/docs/release_notes/ReleaseNotes.doc
labs/jbosstm/trunk/ArjunaJTS/docs/user_guide/AdministrationGuide.doc
labs/jbosstm/trunk/ArjunaJTS/docs/user_guide/ProgrammersGuide.doc
labs/jbosstm/trunk/ArjunaJTS/docs/user_guide/QuickStartGuide.doc
labs/jbosstm/trunk/ArjunaJTS/jts/classes/com/arjuna/ats/internal/jts/ControlWrapper.java
labs/jbosstm/trunk/ArjunaJTS/jts/classes/com/arjuna/ats/internal/jts/interposition/FactoryList.java
labs/jbosstm/trunk/ArjunaJTS/jts/classes/com/arjuna/ats/internal/jts/interposition/resources/arjuna/Interposition.java
labs/jbosstm/trunk/ArjunaJTS/jts/classes/com/arjuna/ats/internal/jts/interposition/resources/restricted/RestrictedInterposition.java
labs/jbosstm/trunk/ArjunaJTS/jts/classes/com/arjuna/ats/internal/jts/orbspecific/ControlImple.java
labs/jbosstm/trunk/ArjunaJTS/jts/classes/com/arjuna/ats/internal/jts/orbspecific/TransactionFactoryImple.java
labs/jbosstm/trunk/ArjunaJTS/jts/classes/com/arjuna/ats/internal/jts/orbspecific/coordinator/ArjunaTransactionImple.java
labs/jbosstm/trunk/ArjunaJTS/jts/classes/com/arjuna/ats/internal/jts/recovery/contact/FactoryContactItem.java
labs/jbosstm/trunk/ArjunaJTS/jts/classes/com/arjuna/ats/jts/TransactionServer.java
labs/jbosstm/trunk/ArjunaJTS/jts/classes/com/arjuna/ats/jts/extensions/Arjuna.java
labs/jbosstm/trunk/ArjunaJTS/jts/classes/com/arjuna/ats/jts/utils/Utility.java
labs/jbosstm/trunk/ArjunaJTS/jts/services/config/transactionservice.conf
labs/jbosstm/trunk/ArjunaJTS/jts/services/scripts/unix/transactionserverservice.sh
labs/jbosstm/trunk/ArjunaJTS/trailmap/README.txt
labs/jbosstm/trunk/ArjunaJTS/trailmap/build.xml
labs/jbosstm/trunk/ArjunaJTS/trailmap/docs/DTP.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/next.xml
labs/jbosstm/trunk/ArjunaJTS/trailmap/docs/part1.xml
labs/jbosstm/trunk/ArjunaJTS/trailmap/docs/part2.xml
labs/jbosstm/trunk/ArjunaJTS/trailmap/docs/part3.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_jts.xml
labs/jbosstm/trunk/ArjunaJTS/trailmap/docs/part5_jts_explicit.xml
labs/jbosstm/trunk/ArjunaJTS/trailmap/docs/part5_jts_implicit.xml
labs/jbosstm/trunk/ArjunaJTS/trailmap/docs/part5_jts_local.xml
labs/jbosstm/trunk/ArjunaJTS/trailmap/docs/part5_testing_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_txoj_banking_deploy.xml
labs/jbosstm/trunk/ArjunaJTS/trailmap/docs/part7.xml
labs/jbosstm/trunk/ArjunaJTS/trailmap/src/com/arjuna/demo/jta/jdbcbank/Bank.java
labs/jbosstm/trunk/ArjunaJTS/trailmap/src/com/arjuna/demo/jta/jdbcbank/BankClient.java
labs/jbosstm/trunk/ArjunaJTS/trailmap/src/com/arjuna/demo/jta/localbank/Account.java
labs/jbosstm/trunk/ArjunaJTS/trailmap/src/com/arjuna/demo/jta/localbank/Bank.java
labs/jbosstm/trunk/ArjunaJTS/trailmap/src/com/arjuna/demo/jta/localbank/BankClient.java
labs/jbosstm/trunk/ArjunaJTS/trailmap/src/com/arjuna/demo/jts/explicitremotebank/AccountResource.java
labs/jbosstm/trunk/ArjunaJTS/trailmap/src/com/arjuna/demo/jts/explicitremotebank/BankClient.java
labs/jbosstm/trunk/ArjunaJTS/trailmap/src/com/arjuna/demo/jts/explicitremotebank/BankImpl.java
labs/jbosstm/trunk/ArjunaJTS/trailmap/src/com/arjuna/demo/jts/explicitremotebank/BankServer.java
labs/jbosstm/trunk/ArjunaJTS/trailmap/src/com/arjuna/demo/jts/localbank/AccountResource.java
labs/jbosstm/trunk/ArjunaJTS/trailmap/src/com/arjuna/demo/jts/localbank/Bank.java
labs/jbosstm/trunk/ArjunaJTS/trailmap/src/com/arjuna/demo/jts/localbank/BankClient.java
labs/jbosstm/trunk/ArjunaJTS/trailmap/src/com/arjuna/demo/jts/remotebank/AccountResource.java
labs/jbosstm/trunk/ArjunaJTS/trailmap/src/com/arjuna/demo/jts/remotebank/BankClient.java
labs/jbosstm/trunk/ArjunaJTS/trailmap/src/com/arjuna/demo/jts/remotebank/BankImpl.java
labs/jbosstm/trunk/ArjunaJTS/trailmap/src/com/arjuna/demo/jts/remotebank/BankServer.java
labs/jbosstm/trunk/ArjunaJTS/trailmap/src/com/arjuna/demo/jts/txojbank/AccountImpl.java
labs/jbosstm/trunk/ArjunaJTS/trailmap/src/com/arjuna/demo/jts/txojbank/BankClient.java
labs/jbosstm/trunk/ArjunaJTS/trailmap/src/com/arjuna/demo/jts/txojbank/BankServer.java
labs/jbosstm/trunk/ArjunaJTS/trailmap/src/com/arjuna/demo/recovery/xaresource/TestXAResourceRecovery.java
labs/jbosstm/trunk/ArjunaJTS/trailmap/src/com/arjuna/demo/recoverymodule/SimpleRecord.java
labs/jbosstm/trunk/ArjunaJTS/trailmap/src/com/arjuna/demo/recoverymodule/SimpleRecoveryModule.java
labs/jbosstm/trunk/ArjunaJTS/trailmap/src/com/arjuna/demo/recoverymodule/TestRecoveryModule.java
labs/jbosstm/trunk/ArjunaJTS/trailmap/src/com/arjuna/demo/simple/HelloClient.java
labs/jbosstm/trunk/ArjunaJTS/trailmap/src/com/arjuna/demo/simple/HelloServer.java
labs/jbosstm/trunk/atsintegration/docbuild/docs/rmi-iiop.xml
labs/jbosstm/trunk/atsintegration/scripts/run-tools.bat
labs/jbosstm/trunk/atsintegration/scripts/run-tools.sh
labs/jbosstm/trunk/common/classes/com/arjuna/common/internal/util/logging/commonPropertyManager.java
labs/jbosstm/trunk/ext/third_party_licenses.txt
Log:
http://jira.jboss.com/jira/browse/JBTM-71
http://jira.jboss.com/jira/browse/JBTM-129
Modified: labs/jbosstm/trunk/ArjunaCore/arjuna/classes/com/arjuna/ats/arjuna/coordinator/TxStats.java
===================================================================
--- labs/jbosstm/trunk/ArjunaCore/arjuna/classes/com/arjuna/ats/arjuna/coordinator/TxStats.java 2006-09-24 05:52:34 UTC (rev 6395)
+++ labs/jbosstm/trunk/ArjunaCore/arjuna/classes/com/arjuna/ats/arjuna/coordinator/TxStats.java 2006-09-24 07:16:18 UTC (rev 6396)
@@ -108,7 +108,7 @@
public static void printStatus (java.io.PrintWriter pw)
{
- pw.println("Arjuna Transaction Service statistics.");
+ pw.println("JBoss Transaction Service statistics.");
pw.println(java.util.Calendar.getInstance().getTime()+"\n");
pw.println("Number of transactions: "+numberOfTransactions());
Modified: labs/jbosstm/trunk/ArjunaCore/arjuna/classes/com/arjuna/ats/internal/arjuna/objectstore/JDBCActionStore.java
===================================================================
--- labs/jbosstm/trunk/ArjunaCore/arjuna/classes/com/arjuna/ats/internal/arjuna/objectstore/JDBCActionStore.java 2006-09-24 05:52:34 UTC (rev 6395)
+++ labs/jbosstm/trunk/ArjunaCore/arjuna/classes/com/arjuna/ats/internal/arjuna/objectstore/JDBCActionStore.java 2006-09-24 07:16:18 UTC (rev 6396)
@@ -284,6 +284,6 @@
private JDBCAccess _txJDBCAccess;
private String _txClassName;
private String _txTableName;
- private static String _defaultTxTableName = "ArjunaTSTxTable";
+ private static String _defaultTxTableName = "JBossTSTxTable";
}
Modified: labs/jbosstm/trunk/ArjunaCore/arjuna/classes/com/arjuna/ats/internal/arjuna/objectstore/JDBCStore.java
===================================================================
--- labs/jbosstm/trunk/ArjunaCore/arjuna/classes/com/arjuna/ats/internal/arjuna/objectstore/JDBCStore.java 2006-09-24 05:52:34 UTC (rev 6395)
+++ labs/jbosstm/trunk/ArjunaCore/arjuna/classes/com/arjuna/ats/internal/arjuna/objectstore/JDBCStore.java 2006-09-24 07:16:18 UTC (rev 6396)
@@ -779,7 +779,7 @@
private JDBCAccess _jdbcAccess;
private String _jdbcAccessClassName;
private String _jdbcTableName;
- private static String _defaultTableName = "ArjunaTSTable";
+ private static String _defaultTableName = "JBossTSTable";
/*
* Class data.
Modified: labs/jbosstm/trunk/ArjunaCore/arjuna/etc/default-CommonLogging-properties.xml
===================================================================
--- labs/jbosstm/trunk/ArjunaCore/arjuna/etc/default-CommonLogging-properties.xml 2006-09-24 05:52:34 UTC (rev 6395)
+++ labs/jbosstm/trunk/ArjunaCore/arjuna/etc/default-CommonLogging-properties.xml 2006-09-24 07:16:18 UTC (rev 6396)
@@ -21,7 +21,7 @@
-->
<!-- $Id: default-CommonLogging-properties.xml 2342 2006-03-30 13:06:17Z $ -->
<!--
- These options are described in the ArjunaTS manual.
+ These options are described in the JBossTS manual.
Defaults are provided here for convenience only.
Please read through this file prior to using the system, and consider
Modified: labs/jbosstm/trunk/ArjunaCore/arjuna/services/config/recoveryservice.conf
===================================================================
--- labs/jbosstm/trunk/ArjunaCore/arjuna/services/config/recoveryservice.conf 2006-09-24 05:52:34 UTC (rev 6395)
+++ labs/jbosstm/trunk/ArjunaCore/arjuna/services/config/recoveryservice.conf 2006-09-24 07:16:18 UTC (rev 6396)
@@ -105,10 +105,10 @@
wrapper.ntservice.name=arjunarm
# Display name of the service
-wrapper.ntservice.displayname=Arjuna Transaction Service - Recovery Manager
+wrapper.ntservice.displayname=JBoss Transaction Service - Recovery Manager
# Description of the service
-wrapper.ntservice.description=The recovery manager service for ArjunaTS
+wrapper.ntservice.description=The recovery manager service for JBosssTS
# Service dependencies. Add dependencies as needed starting from 1
wrapper.ntservice.dependency.1=
Modified: labs/jbosstm/trunk/ArjunaCore/arjuna/services/scripts/unix/recoverymanagerservice.sh
===================================================================
--- labs/jbosstm/trunk/ArjunaCore/arjuna/services/scripts/unix/recoverymanagerservice.sh 2006-09-24 05:52:34 UTC (rev 6395)
+++ labs/jbosstm/trunk/ArjunaCore/arjuna/services/scripts/unix/recoverymanagerservice.sh 2006-09-24 07:16:18 UTC (rev 6396)
@@ -42,7 +42,7 @@
# Application
APP_NAME="arjunarm"
-APP_LONG_NAME="Arjuna Transaction Service Recovery Manager"
+APP_LONG_NAME="JBoss Transaction Service Recovery Manager"
# Wrapper
WRAPPER_CMD="./wrapper"
Modified: labs/jbosstm/trunk/ArjunaCore/docs/install_guide/InstallGuide.doc
===================================================================
(Binary files differ)
Modified: labs/jbosstm/trunk/ArjunaCore/docs/user_guide/FailureRecoveryGuide.doc
===================================================================
(Binary files differ)
Modified: labs/jbosstm/trunk/ArjunaCore/docs/user_guide/ProgrammersGuide.doc
===================================================================
(Binary files differ)
Modified: labs/jbosstm/trunk/ArjunaCore/scripts/run-tools.bat
===================================================================
--- labs/jbosstm/trunk/ArjunaCore/scripts/run-tools.bat 2006-09-24 05:52:34 UTC (rev 6395)
+++ labs/jbosstm/trunk/ArjunaCore/scripts/run-tools.bat 2006-09-24 07:16:18 UTC (rev 6396)
@@ -22,7 +22,7 @@
if "%@HOME_DIRECTORY@%"=="" goto atserror
-rem Setup the environment for the Arjuna Transaction Service
+rem Setup the environment for the JBoss Transaction Service
call "%@HOME_DIRECTORY@%\bin\setup-env.bat"
rem Add ext libraries required for tools
Modified: labs/jbosstm/trunk/ArjunaCore/scripts/run-tools.sh
===================================================================
--- labs/jbosstm/trunk/ArjunaCore/scripts/run-tools.sh 2006-09-24 05:52:34 UTC (rev 6395)
+++ labs/jbosstm/trunk/ArjunaCore/scripts/run-tools.sh 2006-09-24 07:16:18 UTC (rev 6396)
@@ -38,7 +38,7 @@
;;
esac
-# Setup the environment for the Arjuna Transaction Service
+# Setup the environment for the JBoss Transaction Service
. "$@HOME_DIRECTORY@/bin/setup-env.sh"
# Add ext libraries required for tools
Modified: labs/jbosstm/trunk/ArjunaCore/scripts/setup-env.bat
===================================================================
--- labs/jbosstm/trunk/ArjunaCore/scripts/setup-env.bat 2006-09-24 05:52:34 UTC (rev 6395)
+++ labs/jbosstm/trunk/ArjunaCore/scripts/setup-env.bat 2006-09-24 07:16:18 UTC (rev 6396)
@@ -21,7 +21,7 @@
@echo off
rem
-rem Arjuna Transaction Service
+rem Arjuna Transaction Service (now JBoss Transaction Service)
rem
rem Arjuna Technologies Ltd.
rem Copyright 2004
@@ -31,29 +31,29 @@
echo Environment variable JAVA_HOME set to "%JAVA_HOME%"
-if "%ARJUNATS_HOME%"=="" goto jts_home_error
+if "%JBOSSTS_HOME%"=="" goto jts_home_error
-echo Environment variable ARJUNATS_HOME set to "%ARJUNATS_HOME%"
+echo Environment variable JBOSSTS_HOME set to "%JBOSSTS_HOME%"
rem Setup EXT classpath
echo Setting up environment
-set PRODUCT_CLASSPATH=%ARJUNATS_HOME%\lib\@PRODUCT_NAME at .jar
-set PRODUCT_CLASSPATH=%PRODUCT_CLASSPATH%;%ARJUNATS_HOME%\lib\@PRODUCT_NAME at -jacorb.jar
-set PRODUCT_CLASSPATH=%PRODUCT_CLASSPATH%;%ARJUNATS_HOME%\bin\tsmx-tools.jar
-set PRODUCT_CLASSPATH=%PRODUCT_CLASSPATH%;%ARJUNATS_HOME%\etc\
+set PRODUCT_CLASSPATH=%JBOSSTS_HOME%\lib\@PRODUCT_NAME at .jar
+set PRODUCT_CLASSPATH=%PRODUCT_CLASSPATH%;%JBOSSTS_HOME%\lib\@PRODUCT_NAME at -jacorb.jar
+set PRODUCT_CLASSPATH=%PRODUCT_CLASSPATH%;%JBOSSTS_HOME%\bin\tsmx-tools.jar
+set PRODUCT_CLASSPATH=%PRODUCT_CLASSPATH%;%JBOSSTS_HOME%\etc\
-set EXT_CLASSPATH=%ARJUNATS_HOME%\lib\ext\jbossts-common.jar
-set EXT_CLASSPATH=%EXT_CLASSPATH%;%ARJUNATS_HOME%\lib\ext\commons-logging.jar
-set EXT_CLASSPATH=%EXT_CLASSPATH%;%ARJUNATS_HOME%\lib\ext\connector-api.jar
-set EXT_CLASSPATH=%EXT_CLASSPATH%;%ARJUNATS_HOME%\lib\ext\jdbc2_0-stdext.jar
-set EXT_CLASSPATH=%EXT_CLASSPATH%;%ARJUNATS_HOME%\lib\ext\jmxri.jar
-set EXT_CLASSPATH=%EXT_CLASSPATH%;%ARJUNATS_HOME%\lib\ext\jndi.jar
-set EXT_CLASSPATH=%EXT_CLASSPATH%;%ARJUNATS_HOME%\lib\ext\jta-spec1_0_1.jar
-set EXT_CLASSPATH=%EXT_CLASSPATH%;%ARJUNATS_HOME%\lib\ext\log4j-1.2.8.jar
-set EXT_CLASSPATH=%EXT_CLASSPATH%;%ARJUNATS_HOME%\lib\ext\xercesImpl.jar
-set EXT_CLASSPATH=%EXT_CLASSPATH%;%ARJUNATS_HOME%\lib\ext\xmlParserAPIs.jar
+set EXT_CLASSPATH=%JBOSSTS_HOME%\lib\ext\jbossts-common.jar
+set EXT_CLASSPATH=%EXT_CLASSPATH%;%JBOSSTS_HOME%\lib\ext\commons-logging.jar
+set EXT_CLASSPATH=%EXT_CLASSPATH%;%JBOSSTS_HOME%\lib\ext\connector-api.jar
+set EXT_CLASSPATH=%EXT_CLASSPATH%;%JBOSSTS_HOME%\lib\ext\jdbc2_0-stdext.jar
+set EXT_CLASSPATH=%EXT_CLASSPATH%;%JBOSSTS_HOME%\lib\ext\jmxri.jar
+set EXT_CLASSPATH=%EXT_CLASSPATH%;%JBOSSTS_HOME%\lib\ext\jndi.jar
+set EXT_CLASSPATH=%EXT_CLASSPATH%;%JBOSSTS_HOME%\lib\ext\jta-spec1_0_1.jar
+set EXT_CLASSPATH=%EXT_CLASSPATH%;%JBOSSTS_HOME%\lib\ext\log4j-1.2.8.jar
+set EXT_CLASSPATH=%EXT_CLASSPATH%;%JBOSSTS_HOME%\lib\ext\xercesImpl.jar
+set EXT_CLASSPATH=%EXT_CLASSPATH%;%JBOSSTS_HOME%\lib\ext\xmlParserAPIs.jar
set JACORB_HOME=PUT_JACORB_HOME_HERE
set JACORB_CLASSPATH=%JACORB_HOME%\lib\jacorb.jar
@@ -71,7 +71,7 @@
goto end
:jts_home_error
-echo Environment variable ARJUNATS_HOME not set
+echo Environment variable JBOSSTS_HOME not set
goto end
:end
Modified: labs/jbosstm/trunk/ArjunaCore/scripts/setup-env.sh
===================================================================
--- labs/jbosstm/trunk/ArjunaCore/scripts/setup-env.sh 2006-09-24 05:52:34 UTC (rev 6395)
+++ labs/jbosstm/trunk/ArjunaCore/scripts/setup-env.sh 2006-09-24 07:16:18 UTC (rev 6396)
@@ -19,7 +19,7 @@
# @author JBoss Inc.
#
#
-# Arjuna Transaction Service
+# Arjuna Transaction Service (now JBoss Transaction Service)
#
# Arjuna Technologies Ltd.
# Copyright 2004
@@ -35,10 +35,10 @@
else
- if test "x$ARJUNATS_HOME" = "x"
+ if test "x$JBOSSTS_HOME" = "x"
then
- echo Please ensure the ARJUNATS_HOME environment variable is set
+ echo Please ensure the JBOSSTS_HOME environment variable is set
CONTINUE_SETUP=false
fi
@@ -59,7 +59,7 @@
CYGWIN_* | Windows* )
CPS=";"
JACORB_HOME=`echo $JACORB_HOME | sed -e 's;\\\;/;g'`
- ARJUNATS_HOME=`echo $ARJUNATS_HOME | sed -e 's;\\\;/;g'`
+ JBOSSTS_HOME=`echo $JBOSSTS_HOME | sed -e 's;\\\;/;g'`
;;
esac
@@ -68,21 +68,21 @@
echo Setting up environment
-PRODUCT_CLASSPATH="$ARJUNATS_HOME/lib/@PRODUCT_NAME at .jar"
-PRODUCT_CLASSPATH="$PRODUCT_CLASSPATH$CPS$ARJUNATS_HOME/lib/@PRODUCT_NAME at -jacorb.jar"
-PRODUCT_CLASSPATH="$PRODUCT_CLASSPATH$CPS$ARJUNATS_HOME/bin/tsmx-tools.jar"
-PRODUCT_CLASSPATH="$PRODUCT_CLASSPATH$CPS$ARJUNATS_HOME/etc/"
+PRODUCT_CLASSPATH="$JBOSSTS_HOME/lib/@PRODUCT_NAME at .jar"
+PRODUCT_CLASSPATH="$PRODUCT_CLASSPATH$CPS$JBOSSTS_HOME/lib/@PRODUCT_NAME at -jacorb.jar"
+PRODUCT_CLASSPATH="$PRODUCT_CLASSPATH$CPS$JBOSSTS_HOME/bin/tsmx-tools.jar"
+PRODUCT_CLASSPATH="$PRODUCT_CLASSPATH$CPS$JBOSSTS_HOME/etc/"
-EXT_CLASSPATH="$ARJUNATS_HOME/lib/ext/jbossts-common.jar"
-EXT_CLASSPATH="$EXT_CLASSPATH$CPS$ARJUNATS_HOME/lib/ext/commons-logging.jar"
-EXT_CLASSPATH="$EXT_CLASSPATH$CPS$ARJUNATS_HOME/lib/ext/connector-api.jar"
-EXT_CLASSPATH="$EXT_CLASSPATH$CPS$ARJUNATS_HOME/lib/ext/jdbc2_0-stdext.jar"
-EXT_CLASSPATH="$EXT_CLASSPATH$CPS$ARJUNATS_HOME/lib/ext/jmxri.jar"
-EXT_CLASSPATH="$EXT_CLASSPATH$CPS$ARJUNATS_HOME/lib/ext/jndi.jar"
-EXT_CLASSPATH="$EXT_CLASSPATH$CPS$ARJUNATS_HOME/lib/ext/jta-spec1_0_1.jar"
-EXT_CLASSPATH="$EXT_CLASSPATH$CPS$ARJUNATS_HOME/lib/ext/log4j-1.2.8.jar"
-EXT_CLASSPATH="$EXT_CLASSPATH$CPS$ARJUNATS_HOME/lib/ext/xercesImpl.jar"
-EXT_CLASSPATH="$EXT_CLASSPATH$CPS$ARJUNATS_HOME/lib/ext/xmlParserAPIs.jar"
+EXT_CLASSPATH="$JBOSSTS_HOME/lib/ext/jbossts-common.jar"
+EXT_CLASSPATH="$EXT_CLASSPATH$CPS$JBOSSTS_HOME/lib/ext/commons-logging.jar"
+EXT_CLASSPATH="$EXT_CLASSPATH$CPS$JBOSSTS_HOME/lib/ext/connector-api.jar"
+EXT_CLASSPATH="$EXT_CLASSPATH$CPS$JBOSSTS_HOME/lib/ext/jdbc2_0-stdext.jar"
+EXT_CLASSPATH="$EXT_CLASSPATH$CPS$JBOSSTS_HOME/lib/ext/jmxri.jar"
+EXT_CLASSPATH="$EXT_CLASSPATH$CPS$JBOSSTS_HOME/lib/ext/jndi.jar"
+EXT_CLASSPATH="$EXT_CLASSPATH$CPS$JBOSSTS_HOME/lib/ext/jta-spec1_0_1.jar"
+EXT_CLASSPATH="$EXT_CLASSPATH$CPS$JBOSSTS_HOME/lib/ext/log4j-1.2.8.jar"
+EXT_CLASSPATH="$EXT_CLASSPATH$CPS$JBOSSTS_HOME/lib/ext/xercesImpl.jar"
+EXT_CLASSPATH="$EXT_CLASSPATH$CPS$JBOSSTS_HOME/lib/ext/xmlParserAPIs.jar"
JACORB_CLASSPATH="$JACORB_HOME/lib/jacorb.jar"
JACORB_CLASSPATH="$JACORB_CLASSPATH$CPS$JACORB_HOME/lib/idl.jar"
Modified: labs/jbosstm/trunk/ArjunaCore/scripts/start-recovery-manager.sh
===================================================================
--- labs/jbosstm/trunk/ArjunaCore/scripts/start-recovery-manager.sh 2006-09-24 05:52:34 UTC (rev 6395)
+++ labs/jbosstm/trunk/ArjunaCore/scripts/start-recovery-manager.sh 2006-09-24 07:16:18 UTC (rev 6396)
@@ -20,7 +20,7 @@
# @author JBoss Inc.
#
-# Setup the environment for the Arjuna Transaction Service
+# Setup the environment for the JBoss Transaction Service
. "$@HOME_DIRECTORY@/bin/setup-env.sh"
"$JAVA_HOME/bin/java" com.arjuna.ats.arjuna.recovery.RecoveryManager -test
Modified: labs/jbosstm/trunk/ArjunaCore/scripts/start-transaction-service.sh
===================================================================
--- labs/jbosstm/trunk/ArjunaCore/scripts/start-transaction-service.sh 2006-09-24 05:52:34 UTC (rev 6395)
+++ labs/jbosstm/trunk/ArjunaCore/scripts/start-transaction-service.sh 2006-09-24 07:16:18 UTC (rev 6396)
@@ -20,7 +20,7 @@
# @author JBoss Inc.
#
-# Setup the environment for the Arjuna Transaction Service
+# Setup the environment for the JBoss Transaction Service
. "$@HOME_DIRECTORY@/bin/setup-env.sh"
"$JAVA_HOME/bin/java" com.arjuna.ats.jts.TransactionServer -test
Modified: labs/jbosstm/trunk/ArjunaCore/tsmx/etc/jmxbrowser/tools.properties
===================================================================
--- labs/jbosstm/trunk/ArjunaCore/tsmx/etc/jmxbrowser/tools.properties 2006-09-24 05:52:34 UTC (rev 6395)
+++ labs/jbosstm/trunk/ArjunaCore/tsmx/etc/jmxbrowser/tools.properties 2006-09-24 07:16:18 UTC (rev 6396)
@@ -18,7 +18,7 @@
# (C) 2005-2006,
# @author JBoss Inc.
#
-# Arjuna Transaction Service - Tools
+# JBoss Transaction Service - Tools
# JMX Browser
tool.classname=com.arjuna.ats.tools.jmxbrowser.JMXBrowserPlugin
tool.icon.16=/jmxbrowser-icon16.gif
Modified: labs/jbosstm/trunk/ArjunaCore/tsmx/etc/objectstorebrowser/tools.properties
===================================================================
--- labs/jbosstm/trunk/ArjunaCore/tsmx/etc/objectstorebrowser/tools.properties 2006-09-24 05:52:34 UTC (rev 6395)
+++ labs/jbosstm/trunk/ArjunaCore/tsmx/etc/objectstorebrowser/tools.properties 2006-09-24 07:16:18 UTC (rev 6396)
@@ -18,7 +18,7 @@
# (C) 2005-2006,
# @author JBoss Inc.
#
-# Arjuna Transaction Service - Tools
+# JBoss Transaction Service - Tools
# ObjectStore Browser
tool.classname=com.arjuna.ats.tools.objectstorebrowser.ObjectStoreBrowserPlugin
tool.icon.16=/objectstore-icon16.gif
Modified: labs/jbosstm/trunk/ArjunaCore/tsmx/etc/perfgraph/tools.properties
===================================================================
--- labs/jbosstm/trunk/ArjunaCore/tsmx/etc/perfgraph/tools.properties 2006-09-24 05:52:34 UTC (rev 6395)
+++ labs/jbosstm/trunk/ArjunaCore/tsmx/etc/perfgraph/tools.properties 2006-09-24 07:16:18 UTC (rev 6396)
@@ -18,7 +18,7 @@
# (C) 2005-2006,
# @author JBoss Inc.
#
-# Arjuna Transaction Service - Tools
+# JBoss Transaction Service - Tools
# JMX Browser
tool.classname=com.arjuna.ats.tools.perfgraph.PerformanceGraph
tool.icon.16=/perfgraph-icon16.gif
Modified: labs/jbosstm/trunk/ArjunaCore/tsmx/etc/toolsframework.xml
===================================================================
--- labs/jbosstm/trunk/ArjunaCore/tsmx/etc/toolsframework.xml 2006-09-24 05:52:34 UTC (rev 6395)
+++ labs/jbosstm/trunk/ArjunaCore/tsmx/etc/toolsframework.xml 2006-09-24 07:16:18 UTC (rev 6396)
@@ -22,7 +22,7 @@
<tools-framework>
<look-and-feel>
- <title>Arjuna Transaction Service 4.0</title>
+ <title>JBoss Transaction Service</title>
<frame-properties width="800" height="600"/>
</look-and-feel>
Modified: labs/jbosstm/trunk/ArjunaJTA/docs/install_guide/InstallGuide.doc
===================================================================
(Binary files differ)
Modified: labs/jbosstm/trunk/ArjunaJTA/docs/user_guide/ProgrammersGuide.doc
===================================================================
(Binary files differ)
Modified: labs/jbosstm/trunk/ArjunaJTS/docs/release_notes/ReleaseNotes.doc
===================================================================
(Binary files differ)
Modified: labs/jbosstm/trunk/ArjunaJTS/docs/user_guide/AdministrationGuide.doc
===================================================================
(Binary files differ)
Modified: labs/jbosstm/trunk/ArjunaJTS/docs/user_guide/ProgrammersGuide.doc
===================================================================
(Binary files differ)
Modified: labs/jbosstm/trunk/ArjunaJTS/docs/user_guide/QuickStartGuide.doc
===================================================================
(Binary files differ)
Modified: labs/jbosstm/trunk/ArjunaJTS/jts/classes/com/arjuna/ats/internal/jts/ControlWrapper.java
===================================================================
--- labs/jbosstm/trunk/ArjunaJTS/jts/classes/com/arjuna/ats/internal/jts/ControlWrapper.java 2006-09-24 05:52:34 UTC (rev 6395)
+++ labs/jbosstm/trunk/ArjunaJTS/jts/classes/com/arjuna/ats/internal/jts/ControlWrapper.java 2006-09-24 07:16:18 UTC (rev 6396)
@@ -91,8 +91,8 @@
this(c, (Uid) null);
/*
- * Now get the Uid for this control or generate one if it isn't an
- * Arjuna transaction.
+ * Now get the Uid for this control or generate one if it isn't a
+ * JBoss transaction.
*/
try
Modified: labs/jbosstm/trunk/ArjunaJTS/jts/classes/com/arjuna/ats/internal/jts/interposition/FactoryList.java
===================================================================
--- labs/jbosstm/trunk/ArjunaJTS/jts/classes/com/arjuna/ats/internal/jts/interposition/FactoryList.java 2006-09-24 05:52:34 UTC (rev 6395)
+++ labs/jbosstm/trunk/ArjunaJTS/jts/classes/com/arjuna/ats/internal/jts/interposition/FactoryList.java 2006-09-24 07:16:18 UTC (rev 6396)
@@ -87,7 +87,7 @@
/*
* Add the Arjuna OTS transaction recreator as a minimum, i.e., no special
- * action is required to know about Arjuna transactions.
+ * action is required to know about JBoss transactions.
*/
/**
Modified: labs/jbosstm/trunk/ArjunaJTS/jts/classes/com/arjuna/ats/internal/jts/interposition/resources/arjuna/Interposition.java
===================================================================
--- labs/jbosstm/trunk/ArjunaJTS/jts/classes/com/arjuna/ats/internal/jts/interposition/resources/arjuna/Interposition.java 2006-09-24 05:52:34 UTC (rev 6395)
+++ labs/jbosstm/trunk/ArjunaJTS/jts/classes/com/arjuna/ats/internal/jts/interposition/resources/arjuna/Interposition.java 2006-09-24 07:16:18 UTC (rev 6396)
@@ -86,7 +86,7 @@
/*
* Assume that all actions in the imported hierarchy are of the same
- * type, i.e., all Arjuna transactions.
+ * type, i.e., all JBoss transactions.
*
* Because of the way garbage collection works in the ORB we have to
* run an explicit garbage collection phase for finished hierarchies.
Modified: labs/jbosstm/trunk/ArjunaJTS/jts/classes/com/arjuna/ats/internal/jts/interposition/resources/restricted/RestrictedInterposition.java
===================================================================
--- labs/jbosstm/trunk/ArjunaJTS/jts/classes/com/arjuna/ats/internal/jts/interposition/resources/restricted/RestrictedInterposition.java 2006-09-24 05:52:34 UTC (rev 6395)
+++ labs/jbosstm/trunk/ArjunaJTS/jts/classes/com/arjuna/ats/internal/jts/interposition/resources/restricted/RestrictedInterposition.java 2006-09-24 07:16:18 UTC (rev 6396)
@@ -67,7 +67,7 @@
/*
* Assume that all actions in the imported hierarchy are of the same
- * type, i.e., all Arjuna transactions.
+ * type, i.e., all JBoss transactions.
*
* Because of the way garbage collection works in the ORB we have to
* run an explicit garbage collection phase for finished hierarchies.
Modified: labs/jbosstm/trunk/ArjunaJTS/jts/classes/com/arjuna/ats/internal/jts/orbspecific/ControlImple.java
===================================================================
--- labs/jbosstm/trunk/ArjunaJTS/jts/classes/com/arjuna/ats/internal/jts/orbspecific/ControlImple.java 2006-09-24 05:52:34 UTC (rev 6395)
+++ labs/jbosstm/trunk/ArjunaJTS/jts/classes/com/arjuna/ats/internal/jts/orbspecific/ControlImple.java 2006-09-24 07:16:18 UTC (rev 6396)
@@ -61,7 +61,7 @@
* size of all of the transaction objects, we keep the information
* separate in the TransactionReaper. (Since it already needs to have this
* information anyway this is no extra burden.) It also means that we can
- * support non-Arjuna transactions: if we were to add a new method to the
+ * support non-JBoss transactions: if we were to add a new method to the
* control (get_timeout, say) then this would be Arjuna specific.
*/
@@ -462,7 +462,7 @@
catch (Exception e)
{
/*
- * Not an Arjuna transaction, so allocate any Uid.
+ * Not an JBoss transaction, so allocate any Uid.
*/
_theUid = new Uid();
Modified: labs/jbosstm/trunk/ArjunaJTS/jts/classes/com/arjuna/ats/internal/jts/orbspecific/TransactionFactoryImple.java
===================================================================
--- labs/jbosstm/trunk/ArjunaJTS/jts/classes/com/arjuna/ats/internal/jts/orbspecific/TransactionFactoryImple.java 2006-09-24 05:52:34 UTC (rev 6395)
+++ labs/jbosstm/trunk/ArjunaJTS/jts/classes/com/arjuna/ats/internal/jts/orbspecific/TransactionFactoryImple.java 2006-09-24 07:16:18 UTC (rev 6396)
@@ -343,7 +343,7 @@
catch (Exception e)
{
/*
- * Not an Arjuna transaction, so allocate any Uid.
+ * Not a JBoss transaction, so allocate any Uid.
*/
theUid = new Uid();
Modified: labs/jbosstm/trunk/ArjunaJTS/jts/classes/com/arjuna/ats/internal/jts/orbspecific/coordinator/ArjunaTransactionImple.java
===================================================================
--- labs/jbosstm/trunk/ArjunaJTS/jts/classes/com/arjuna/ats/internal/jts/orbspecific/coordinator/ArjunaTransactionImple.java 2006-09-24 05:52:34 UTC (rev 6395)
+++ labs/jbosstm/trunk/ArjunaJTS/jts/classes/com/arjuna/ats/internal/jts/orbspecific/coordinator/ArjunaTransactionImple.java 2006-09-24 07:16:18 UTC (rev 6396)
@@ -1929,7 +1929,7 @@
* OTS lets a thread suspend/resume contexts at will. Potential for memory
* leaks in C++ version, but not Java!!
*
- * Currently we assume that the hierarchy will be Arjuna transactions so we
+ * Currently we assume that the hierarchy will be JBoss transactions so we
* can get the parents of transactions. If it is not then we could simply
* just call get_txcontext on the control!
*/
@@ -2042,7 +2042,7 @@
* can't cope with mixed transaction types anyway! If we
* got here then the root transaction must be an Arjuna
* transaction, so the nested transactions *must* also
- * be Arjuna transactions!
+ * be JBoss transactions!
*/
UidCoordinator uidCoord = Helper.getUidCoordinator(context.parents[index].coord);
Modified: labs/jbosstm/trunk/ArjunaJTS/jts/classes/com/arjuna/ats/internal/jts/recovery/contact/FactoryContactItem.java
===================================================================
--- labs/jbosstm/trunk/ArjunaJTS/jts/classes/com/arjuna/ats/internal/jts/recovery/contact/FactoryContactItem.java 2006-09-24 05:52:34 UTC (rev 6395)
+++ labs/jbosstm/trunk/ArjunaJTS/jts/classes/com/arjuna/ats/internal/jts/recovery/contact/FactoryContactItem.java 2006-09-24 07:16:18 UTC (rev 6396)
@@ -210,7 +210,7 @@
}
/**
- * Constructor used in normal Arjuna Transaction service application to
+ * Constructor used in normal JBoss Transaction service application to
* identify the (or an) ArjunaFactory in this process
*/
Modified: labs/jbosstm/trunk/ArjunaJTS/jts/classes/com/arjuna/ats/jts/TransactionServer.java
===================================================================
--- labs/jbosstm/trunk/ArjunaJTS/jts/classes/com/arjuna/ats/jts/TransactionServer.java 2006-09-24 05:52:34 UTC (rev 6395)
+++ labs/jbosstm/trunk/ArjunaJTS/jts/classes/com/arjuna/ats/jts/TransactionServer.java 2006-09-24 07:16:18 UTC (rev 6396)
@@ -154,7 +154,7 @@
if (printReady)
System.out.println("Ready");
else
- System.out.println("ArjunaTS OTS Server startup.");
+ System.out.println("JBossTS OTS Server startup.");
if (resolver == com.arjuna.orbportability.Services.BIND_CONNECT)
myOA.run(com.arjuna.orbportability.Services.transactionService);
@@ -166,7 +166,7 @@
System.err.println("TransactionServer caught exception "+e2);
}
- System.out.println("ArjunaTS OTS Server shutdown");
+ System.out.println("JBossTS OTS Server shutdown");
theOTS = null;
Modified: labs/jbosstm/trunk/ArjunaJTS/jts/classes/com/arjuna/ats/jts/extensions/Arjuna.java
===================================================================
--- labs/jbosstm/trunk/ArjunaJTS/jts/classes/com/arjuna/ats/jts/extensions/Arjuna.java 2006-09-24 05:52:34 UTC (rev 6395)
+++ labs/jbosstm/trunk/ArjunaJTS/jts/classes/com/arjuna/ats/jts/extensions/Arjuna.java 2006-09-24 07:16:18 UTC (rev 6396)
@@ -32,7 +32,7 @@
package com.arjuna.ats.jts.extensions;
/**
- * To get the formatID used to represent Arjuna transactions
+ * To get the formatID used to represent JBoss transactions
* to the system.
*
* @author Mark Little (mark at arjuna.com)
Modified: labs/jbosstm/trunk/ArjunaJTS/jts/classes/com/arjuna/ats/jts/utils/Utility.java
===================================================================
--- labs/jbosstm/trunk/ArjunaJTS/jts/classes/com/arjuna/ats/jts/utils/Utility.java 2006-09-24 05:52:34 UTC (rev 6395)
+++ labs/jbosstm/trunk/ArjunaJTS/jts/classes/com/arjuna/ats/jts/utils/Utility.java 2006-09-24 07:16:18 UTC (rev 6396)
@@ -143,7 +143,7 @@
/*
* Any need for the inverse operation?
- * Could easily do it for Arjuna transactions only.
+ * Could easily do it for JBoss transactions only.
*/
public static com.arjuna.ats.arjuna.xa.XID getXid (Uid uid, boolean branch) throws IllegalStateException
@@ -187,7 +187,7 @@
}
/**
- * If this control refers to an Arjuna transaction then return its native
+ * If this control refers to an JBoss transaction then return its native
* Uid representation. Otherwise return Uid.nullUid().
*/
Modified: labs/jbosstm/trunk/ArjunaJTS/jts/services/config/transactionservice.conf
===================================================================
--- labs/jbosstm/trunk/ArjunaJTS/jts/services/config/transactionservice.conf 2006-09-24 05:52:34 UTC (rev 6395)
+++ labs/jbosstm/trunk/ArjunaJTS/jts/services/config/transactionservice.conf 2006-09-24 07:16:18 UTC (rev 6396)
@@ -102,13 +102,13 @@
# service can then be reinstalled.
# Name of the service
-wrapper.ntservice.name=arjunats
+wrapper.ntservice.name=jbossts
# Display name of the service
-wrapper.ntservice.displayname=Arjuna Transaction Service - Transaction Server
+wrapper.ntservice.displayname=JBoss Transaction Service - Transaction Server
# Description of the service
-wrapper.ntservice.description=The transaction server service for ArjunaTS
+wrapper.ntservice.description=The transaction server service for JBossTS
# Service dependencies. Add dependencies as needed starting from 1
wrapper.ntservice.dependency.1=
Modified: labs/jbosstm/trunk/ArjunaJTS/jts/services/scripts/unix/transactionserverservice.sh
===================================================================
--- labs/jbosstm/trunk/ArjunaJTS/jts/services/scripts/unix/transactionserverservice.sh 2006-09-24 05:52:34 UTC (rev 6395)
+++ labs/jbosstm/trunk/ArjunaJTS/jts/services/scripts/unix/transactionserverservice.sh 2006-09-24 07:16:18 UTC (rev 6396)
@@ -41,8 +41,8 @@
fi
# Application
-APP_NAME="arjunats"
-APP_LONG_NAME="Arjuna Transaction Service - Transaction Service"
+APP_NAME="jbossts"
+APP_LONG_NAME="JBoss Transaction Service - Transaction Service"
# Wrapper
WRAPPER_CMD="./wrapper"
Deleted: labs/jbosstm/trunk/ArjunaJTS/orbportability/docs/programmers_guide/ORB Portability Layer - Programmers Guide.doc
===================================================================
(Binary files differ)
Copied: labs/jbosstm/trunk/ArjunaJTS/orbportability/docs/programmers_guide/ProgrammersGuide.doc (from rev 6394, labs/jbosstm/trunk/ArjunaJTS/orbportability/docs/programmers_guide/ORB Portability Layer - Programmers Guide.doc)
===================================================================
(Binary files differ)
Modified: labs/jbosstm/trunk/ArjunaJTS/trailmap/README.txt
===================================================================
--- labs/jbosstm/trunk/ArjunaJTS/trailmap/README.txt 2006-09-24 05:52:34 UTC (rev 6395)
+++ labs/jbosstm/trunk/ArjunaJTS/trailmap/README.txt 2006-09-24 07:16:18 UTC (rev 6396)
@@ -28,12 +28,12 @@
The sample application requires version 1.5.1 or later.
- The PATH and CLASSPATH environment variables need to be set
-appropriately to use Arjuna Transaction Service.
+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) which you can either source, or
use to input into your own environment. These scripts are located in
- in the directory <arjunats_install_root>/bin/
+ in the directory <jbossts_install_root>/bin/
JNDI is recommended way to use XADataSource because it isolates the application from the
different jdbc implementations. The JNDI implementation, that the jdbcbank sample uses is fscontext.jar,
@@ -47,7 +47,7 @@
From a command prompt, go (or 'cd') to the directory containing the
build.xml file (<jbossjts_install_root>/trailmap) and type 'ant'.
- Add the generated file named arjunats-demo.jar and located under
+ Add the generated file named jbossts-demo.jar and located under
<jbossjts_install_root>/trailmap/lib in you CLASSPATH environment
variable.
Modified: labs/jbosstm/trunk/ArjunaJTS/trailmap/build.xml
===================================================================
--- labs/jbosstm/trunk/ArjunaJTS/trailmap/build.xml 2006-09-24 05:52:34 UTC (rev 6395)
+++ labs/jbosstm/trunk/ArjunaJTS/trailmap/build.xml 2006-09-24 07:16:18 UTC (rev 6396)
@@ -27,11 +27,11 @@
-->
<!--
- This is the build script for the Arjuna Transactions product trailmap
+ This is the build script for the JBoss Transactions product trailmap
it has the capability to build the trailmap. Consult the trailmap
itself for more information <ats_install_root>/trailmap/html/index.html
-->
-<project name="ArjunaTS_TrailMap" default="buildjar" basedir=".">
+<project name="JBossTS_TrailMap" default="buildjar" basedir=".">
<!-- Where the transaction has been installed to, this should not need changing by default -->
<property name="jbosstshome" value=".."/>
@@ -118,7 +118,7 @@
<arg value="${src}/com/arjuna/demo/jts/explicitremotebank/Bank.idl"/>
</java>
- <!-- Create the stub classes for the Arjuna Transactional-Objects for Java extension Bank sample -->
+ <!-- Create the stub classes for the JBoss Transactional-Objects for Java extension Bank sample -->
<java classname="org.jacorb.idl.parser" fork="yes">
<classpath>
<fileset dir="${jacorb-home}/lib" includes="*.jar"/>
Deleted: labs/jbosstm/trunk/ArjunaJTS/trailmap/docs/ArjunaTS_Configuration.xml
===================================================================
--- labs/jbosstm/trunk/ArjunaJTS/trailmap/docs/ArjunaTS_Configuration.xml 2006-09-24 05:52:34 UTC (rev 6395)
+++ labs/jbosstm/trunk/ArjunaJTS/trailmap/docs/ArjunaTS_Configuration.xml 2006-09-24 07:16:18 UTC (rev 6396)
@@ -1,558 +0,0 @@
-<?xml version="1.0"?>
-<!--
- JBoss, Home of Professional Open Source
- Copyright 2006, JBoss Inc., and individual contributors as indicated
- by the @authors tag. All rights reserved.
- See the copyright.txt in the distribution for a full listing
- of individual contributors.
- This copyrighted material is made available to anyone wishing to use,
- modify, copy, or redistribute it subject to the terms and conditions
- of the GNU General Public License, v. 2.0.
- This program is distributed in the hope that it will be useful, but WITHOUT A
- WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS FOR A
- PARTICULAR PURPOSE. See the GNU General Public License for more details.
- You should have received a copy of the GNU General Public License,
- v. 2.0 along with this distribution; if not, write to the Free Software
- Foundation, Inc., 51 Franklin Street, Fifth Floor, Boston,
- MA 02110-1301, USA.
-
- (C) 2005-2006,
- @author JBoss Inc.
--->
-<page title="Arjuna Technologies Limited: Trail map: Configuring the Arjuna Transaction Service" rootpath="../..">
- <header>
- Trail map: ArjunaTS Configuration
- </header>
- <content>
- <navigation>
- <links include="includes/www_arjuna_com_navigation.xml"/>
- <links include="includes/trailmap_navigation.xml"/>
- <links title="Navigation">
- <link ref="index.html">Home</link>
- </links>
- <links include="includes/trailmap_additional.xml"/>
- </navigation>
- <area title="Configuring the Arjuna 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 ArjunaTS.
- Basically, the behaviour of the ArjunaTS product is configurable through property
- attributes. Although these property attributes may be specified as command line
- 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
- </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>
-<pre>
-<property>
- name="a_name"
- value="a_value"
-</property>
-</pre>
-</blockquote>
-
-<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 ArjunaTS. </p>
- <p>The following table describes some properties in the arjuna-properties.xml, where:</p>
- <ul>
- <li>
- <b>Name</b> : indicates the name of the property</li>
- <li>
- <b>Description</b>: explain the aim of the property</li>
- <li>
- <b>Possible Value</b>: indicates possible value the property can have</li>
- <li>
- <b>Default</b>
- <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%">
- <b>Name</b>
- </td>
- <td width="25%">
- <b>Description</b>
- </td>
- <td width="10%">
- <b>Possible Value</b>
- </td>
- <td width="27%">
- <b>Default Value</b>
- </td>
- </tr>
-
- <tr>
- <td>com.arjuna.ats.arjuna.<br/>objectstore.localOSRoot</td>
- <td>By default, all object states will be stored within the "defaultStore"
- subdirectory of the object store root. However, this subdirectory can be
- changed by setting the localOSRoot property variable accordingly</td>
- <td>Directory name</td>
- <td>defaultStore</td>
- </tr>
- <tr>
- <td>com.arjuna.ats.arjuna.<br/>objectstore.objectStoreDir</td>
- <td>Specify the location of the ObjectStore</td>
- <td>Directory name</td>
- <td>PutObjectStoreDirHere</td>
- </tr>
- <tr>
- <td>com.arjuna.ats.arjuna.common.varDir</td>
- <td>ArjunaTS needs to be able to write temporary files to a well known location
- during execution. By default this location is var. However, by setting the
- varDir property variable this can be overridden.</td>
- <td>Directory name</td>
- <td>var/tmp</td>
- </tr>
- </table>
- <h4>ObjectStore management</h4>
-The ArjunaTS layer requires an object store for transaction management <a class="linkscoloured" href="DTP.html#RecoveryLog">logs</a>. Within
-the transaction service installation, object store is updated regularly whenever
-transactions are created, or when Transactional Objects for Java is used. In a
-failure free environment, the only object states which should reside within the
-object store are those representing objects created with the Transactional Objects
-for Java API. However, if failures occur, transaction logs may remain in the object
-store until crash recovery facilities have resolved the transactions they represent.
-As such it is very important that the contents of the object store are not deleted
-without due care and attention, as this will make it impossible to resolve in
-doubt transactions. In addition, if multiple users share the same object store
-it is important that they realise this and do not simply delete the contents of
-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
- during the ArjunaTS installation. At any time, the location of the ObjectStore
- may be changed.</p>
- <h4>Configuring Output</h4>
- <p>Sometimes it is desirable, mainly in case of debugging, to have some form of
- output during execution to trace internal actions performed. ArjunaTS uses the
- logging tracing mechanism provided by the Arjuna Common Logging Framework (CLF)
- version 2.4, which provides a high level interface that hides differences that
- exist between logging APIs such Jakarta log4j, JDK 1.4 logging API or dotnet
- logging API.</p>
- <p>With the CLF applications make logging calls on commonLogger objects. These
- commonLogger objects pass log messages to Handler for publication. Both commonLoggers
- and Handlers may use logging Levels to decide if they are interested in a particular
- log message. Each log message has an associated log Level, that gives the importance
- and urgency of a log message. The set of possible Log Levels are DEBUG, INFO,
- WARN, ERROR and FATAL. Defined Levels are ordered according to their integer
- values as follows: DEBUG < INFO < WARN < ERROR < FATAL. </p>
- <p> The CLF provides an extension to filter logging messages according to finer
- granularity an application may define. That is, when a log message is provided
- to the commonLogger with the DEBUG level, additional conditions can be specified
- to determine if the log message is enabled or not. <br/>
- <b>Note</b>: These conditions are applied if and only the DEBUG level is enabled
- and the log request performed by the application specifies debugging granularity.
- <br/>
- When enabled, Debugging is filtered conditionally on three variables: </p>
- <ul>
- <li> Debugging level: this is where the log request with the DEBUG Level is
- generated from, e.g., constructors or basic methods.</li>
- <li> Visibility level: the visibility of the constructor, method, etc. that
- generates the debugging.</li>
- <li> Facility code: for instance the package or sub-module within which debugging
- is generated, e.g., the object store.</li>
- </ul>
- <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. ArjunaTS uses the default Debugging level and the default Visibility
- level provided by CLF, but it defines its own Facility Code. ArjunaJTS 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 ArjunaTS are defined below:
-</p>
- <ul>
- <li>Debugging level – ArjunaTS uses the default values defined in the class
- com.arjuna.common.util.logging.CommonDebugLevel </li>
- </ul>
- <table width="83%" border="1">
- <tr bgcolor="#8BD5FC">
- <td width="33%">
- <div align="center">
- <strong>Debug Level</strong>
- </div>
- </td>
- <td width="24%">
- <div align="center">
- <strong>Value</strong>
- </div>
- </td>
- <td width="43%">
- <div align="center">
- <strong>Description</strong>
- </div>
- </td>
- </tr>
- <tr>
- <td>NO_DEBUGGING</td>
- <td>
- <font face="Courier New, Courier, mono">0x0000</font>
- </td>
- <td>A commonLogger object assigned with this values discard all debug requests</td>
- </tr>
- <tr>
- <td>CONSTRUCTORS</td>
- <td>
- <font face="Courier New, Courier, mono"> 0x0001</font>
- </td>
- <td>Diagnostics from constructors</td>
- </tr>
- <tr>
- <td>DESTRUCTORS</td>
- <td>
- <font face="Courier New, Courier, mono">0x0002</font>
- </td>
- <td>Diagnostics from finalizers.</td>
- </tr>
- <tr>
- <td>CONSTRUCT_AND_DESTRUCT</td>
- <td>
- <font face="Courier New, Courier, mono">CONSTRUCTORS | DESTRUCTORS</font>
- </td>
- <td>Diagnostics from constructors and finalizers</td>
- </tr>
- <tr>
- <td>FUNCTIONS</td>
- <td>
- <font face="Courier New, Courier, mono">0x010</font>
- </td>
- <td>Diagnostics from functions</td>
- </tr>
- <tr>
- <td>OPERATORS</td>
- <td>
- <font face="Courier New, Courier, mono">0x020</font>
- </td>
- <td>Diagnostics from operators, such as equals</td>
- </tr>
- <tr>
- <td>FUNCS_AND_OPS</td>
- <td>
- <font face="Courier New, Courier, mono">FUNCTIONS | OPERATORS</font>
- </td>
- <td>Diagnostics from functions and operations.</td>
- </tr>
- <tr>
- <td>ALL_NON_TRIVIAL</td>
- <td>
- <font face="Courier New, Courier, mono">CONSTRUCT_AND_DESTRUCT | FUNCTIONS
- | OPERATORS</font>
- </td>
- <td>Diagnostics from all non-trivial operations</td>
- </tr>
- <tr>
- <td>TRIVIAL_FUNCS</td>
- <td>
- <font face="Courier New, Courier, mono">0x0100</font>
- </td>
- <td>Diagnostics from trivial functions.</td>
- </tr>
- <tr>
- <td>TRIVIAL_OPERATORS:</td>
- <td>
- <font face="Courier New, Courier, mono">0x0200</font>
- </td>
- <td>Diagnostics from trivial operations, and operators.</td>
- </tr>
- <tr>
- <td> ALL_TRIVIAL</td>
- <td>
- <font face="Courier New, Courier, mono">TRIVIAL_FUNCS | TRIVIAL_OPERATORS</font>
- </td>
- <td>Diagnostics from all trivial operations</td>
- </tr>
- <tr>
- <td>FULL_DEBUGGING</td>
- <td>
- <font face="Courier New, Courier, mono">0xffff</font>
- </td>
- <td>Full diagnostics.</td>
- </tr>
- </table>
- <ul>
- <li>Visibility level – ArjunaTS uses the default values defined in the class
- com.arjuna.common.util.logging.CommonVisibilityLevel </li>
- </ul>
- <table width="83%" border="1">
- <tr bgcolor="#8BD5FC">
- <td width="33%">
- <div align="center">
- <strong>Debug Level</strong>
- </div>
- </td>
- <td width="24%">
- <div align="center">
- <strong>Value</strong>
- </div>
- </td>
- <td width="43%">
- <div align="center">
- <strong>Description</strong>
- </div>
- </td>
- </tr>
- <tr>
- <td>VIS_NONE</td>
- <td>
- <font face="Courier New, Courier, mono">0x0000</font>
- </td>
- <td>No Diagnostic</td>
- </tr>
- <tr>
- <td>VIS_PRIVATE</td>
- <td>
- <font face="Courier New, Courier, mono">0x0001</font>
- </td>
- <td>only from private methods.</td>
- </tr>
- <tr>
- <td>VIS_PROTECTED</td>
- <td>
- <font face="Courier New, Courier, mono">0x0002</font>
- </td>
- <td>only from protected methods.</td>
- </tr>
- <tr>
- <td>VIS_PUBLIC</td>
- <td>
- <font face="Courier New, Courier, mono">0x0004</font>
- </td>
- <td>only from public methods.</td>
- </tr>
- <tr>
- <td>VIS_PACKAGE</td>
- <td>
- <font face="Courier New, Courier, mono">0x0008</font>
- </td>
- <td>only from package methods.</td>
- </tr>
- <tr>
- <td>VIS_ALL</td>
- <td>
- <font face="Courier New, Courier, mono">0xffff</font>
- </td>
- <td>Full Diagnostic</td>
- </tr>
- </table>
- <ul>
- <li>Facility Code – ArjunaTS uses the following values </li>
- </ul>
- <table width="83%" border="1">
- <tr bgcolor="#8BD5FC">
- <td>
- <div align="center">
- <strong>Facility Code Level </strong>
- </div>
- </td>
- <td>
- <div align="center">
- <strong>Value</strong>
- </div>
- </td>
- <td>
- <div align="center">
- <strong>Description</strong>
- </div>
- </td>
- </tr>
- <tr>
- <td>FAC_ATOMIC_ACTION</td>
- <td>
- <font face="Courier New, Courier, mono">0x00000001</font>
- </td>
- <td>atomic action core module</td>
- </tr>
- <tr>
- <td>FAC_BUFFER_MAN</td>
- <td>
- <font face="Courier New, Courier, mono">0x00000004</font>
- </td>
- <td>state management (buffer) classes</td>
- </tr>
- <tr>
- <td>FAC_ABSTRACT_REC</td>
- <td>
- <font face="Courier New, Courier, mono">0x00000008</font>
- </td>
- <td>abstract records</td>
- </tr>
- <tr>
- <td>FAC_OBJECT_STORE</td>
- <td>
- <font face="Courier New, Courier, mono">0x00000010</font>
- </td>
- <td>object store implementations</td>
- </tr>
- <tr>
- <td> FAC_STATE_MAN</td>
- <td>
- <font face="Courier New, Courier, mono">0x00000020</font>
- </td>
- <td>state management and StateManager)</td>
- </tr>
- <tr>
- <td>FAC_SHMEM</td>
- <td>
- <font face="Courier New, Courier, mono">0x00000040 </font>
- </td>
- <td>shared memory implementation classes</td>
- </tr>
- <tr>
- <td>FAC_GENERAL</td>
- <td>
- <font face="Courier New, Courier, mono">0x00000080</font>
- </td>
- <td>general classes</td>
- </tr>
- <tr>
- <td>FAC_CRASH_RECOVERY</td>
- <td>
- <font face="Courier New, Courier, mono">0x00000800</font>
- </td>
- <td>detailed trace of crash recovery module and classes</td>
- </tr>
- <tr>
- <td>FAC_THREADING</td>
- <td>
- <font face="Courier New, Courier, mono">0x00002000</font>
- </td>
- <td>threading classes</td>
- </tr>
- <tr>
- <td>FAC_JDBC</td>
- <td>
- <font face="Courier New, Courier, mono">0x00008000</font>
- </td>
- <td>JDBC 1.0 and 2.0 support</td>
- </tr>
- <tr>
- <td>FAC_RECOVERY_NORMAL</td>
- <td>
- <font face="Courier New, Courier, mono">0x00040000</font>
- </td>
- <td>normal output for crash recovery manager</td>
- </tr>
- </table>
- <p>To ensure appropriate output, it is necessary to set some of the finer debug
- properties explicitly as follows:</p>
- <pre> <properties>
- <!-- CLF 2.4 properties -->
- <property
- name="com.arjuna.common.util.logging.DebugLevel"
- value="0x00000000"/>
- <property
- name="com.arjuna.common.util.logging.FacilityLevel"
- value="0xffffffff"/>
- <property
- name="com.arjuna.common.util.logging.VisibilityLevel"
- value="0xffffffff"/>
- <property
- name="com.arjuna.common.util.logger"
- value="log4j"/>
- </properties></pre>
- <p>By default, debugging messages are not enabled since the DebugLevel is set
- to NO_DEBUGGING (<font face="Courier New, Courier, mono">0x00000000</font>).
- You can enable debugging by providing one of the appropriate value listed above
- - for instance with you wish to see all internal actions performed by the RecoveryManager
- to recover transactions from a failure set the DebugLevel to FULL_DEBUGGING
- (<font face="Courier New, Courier, mono">0xffffffff</font>) and the FacilityCode
- Level FAC_CRASH_RECOVERY. </p>
- <p>
- <strong>Note</strong>: To enable finger debug messages, the logging level should
- be set to the DEBUG level as described below.</p>
- <p>From the program point of view a same API is used whatever the underlying logging
- mechanism, but from a configuration point of view is that the user is totally
- responsible for the configuration of the underlying logging system. Hence, the
- properties of the underlying log system are configured in a manner specific
- to that log system, e.g., a log4j.properties file in the case that log4j logging
- is used. To set the logging level to the DEBUG value, the log4j.properties file
- can be edited to set that value. </p>
- <p>The property <font face="Courier New, Courier, mono">com.arjuna.common.util.logger</font>
- allows to select the underlying logging system. Possible value are listed in
- the following table.</p>
- <table width="93%" border="1">
- <tr bgcolor="#8BD5FC">
- <td width="14%">
- <div align="center">
- <strong>Property Value</strong>
- </div>
- </td>
- <td width="86%">
- <div align="center">
- <strong>Description</strong>
- </div>
- </td>
- </tr>
- <tr>
- <td>
- <font face="Courier New, Courier, mono">log4j</font>
- </td>
- <td>Log4j logging (log4j classes must be available in the classpath); configuration
- through the log4j.properties file, which is picked up from the CLASSPATH
- or given through a System property: <font face="Courier New, Courier, mono">log4j.configuration</font>
- </td>
- </tr>
- <tr>
- <td>
- <font face="Courier New, Courier, mono">jdk14</font>
- </td>
- <td>JDK 1.4 logging API (only supported on JVMs of version 1.4 or higher).
- Configuration is done through a file logging.properties in the jre/lib directory.</td>
- </tr>
- <tr>
- <td>
- <font face="Courier New, Courier, mono">simple</font>
- </td>
- <td>Selects the simple JDK 1.1 compatible console-based logger provided by
- Jakarta Commons Logging</td>
- </tr>
- <tr>
- <td>
- <font face="Courier New, Courier, mono">csf</font>
- </td>
- <td>Selects CSF-based logging (CSF embeddor must be available)</td>
- </tr>
- <tr>
- <td>
- <font face="Courier New, Courier, mono">jakarta</font>
- </td>
- <td>Uses the default log system selection algorithm of the Jakarta Commons
- Logging framework</td>
- </tr>
- <tr>
- <td>
- <font face="Courier New, Courier, mono">dotnet</font>
- </td>
- <td>Selects a .net logging implementation <br/>
- Since a dotnet logger is not currently implemented, this is currently identical
- to <font face="Courier New, Courier, mono">simple</font>. Simple is a purely
- JDK1.1 console-based log implementation.</td>
- </tr>
- <tr>
- <td>
- <font face="Courier New, Courier, mono">avalon</font>
- </td>
- <td>Uses the Avalon Logkit implementation</td>
- </tr>
- <tr>
- <td>
- <font face="Courier New, Courier, mono">noop</font>
- </td>
- <td>Disables all logging </td>
- </tr>
- </table>
- </html>
- </area>
- </content>
- <footer/>
-</page>
Deleted: labs/jbosstm/trunk/ArjunaJTS/trailmap/docs/ArjunaTS_ORBPortability.xml
===================================================================
--- labs/jbosstm/trunk/ArjunaJTS/trailmap/docs/ArjunaTS_ORBPortability.xml 2006-09-24 05:52:34 UTC (rev 6395)
+++ labs/jbosstm/trunk/ArjunaJTS/trailmap/docs/ArjunaTS_ORBPortability.xml 2006-09-24 07:16:18 UTC (rev 6396)
@@ -1,218 +0,0 @@
-<?xml version="1.0"?>
-<!--
- JBoss, Home of Professional Open Source
- Copyright 2006, JBoss Inc., and individual contributors as indicated
- by the @authors tag. All rights reserved.
- See the copyright.txt in the distribution for a full listing
- of individual contributors.
- This copyrighted material is made available to anyone wishing to use,
- modify, copy, or redistribute it subject to the terms and conditions
- of the GNU General Public License, v. 2.0.
- This program is distributed in the hope that it will be useful, but WITHOUT A
- WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS FOR A
- PARTICULAR PURPOSE. See the GNU General Public License for more details.
- You should have received a copy of the GNU General Public License,
- v. 2.0 along with this distribution; if not, write to the Free Software
- Foundation, Inc., 51 Franklin Street, Fifth Floor, Boston,
- MA 02110-1301, USA.
-
- (C) 2005-2006,
- @author JBoss Inc.
--->
-<page title="Arjuna Technologies Limited: Trail map: ORB Portability" rootpath="../..">
- <header> Trail map: ORB Portability </header>
- <content>
- <navigation>
- <links include="includes/www_arjuna_com_navigation.xml"/>
- <links include="includes/trailmap_navigation.xml"/>
- <links title="Navigation">
- <link ref="index.html">Home</link>
- </links>
- <links include="includes/trailmap_additional.xml"/>
- </navigation>
- <area title="ORB Portability">
- <html>
- <h4>Introduction</h4>
- <p>Many ORBs currently in use support different versions of CORBA and/or the Java
- language mapping.<br>
- The Arjuna Transaction Service only supports the new Portable Object Adapter
- (POA) architecture described in the CORBA 2.3 specification as a replacement
- for the Basic Object Adapter (BOA). Unlike the BOA, which was weakly specified
- and led to a number of different (and often conflicting) implementations, the
- POA was deliberately designed to reduce the differences between ORB implementations,
- and thus minimise the amount of re-coding that would need to be done when porting
- applications from one ORB to another. However, there is still scope for slight
- differences between ORB implementations, notably in the area of threading. Note,
- instead of talking about the POA, this manual will consider the Object Adapter</br>
- (OA).</p>
- <p>Because the Arjuna Transaction Service must be able to run on a number of different
- ORBs, we have developed an ORB portability interface which allows entire applications
- to be moved between ORBs with little or no modifications. This portability interface
- is available to the application programmer in the form of several Java classes.
-</p>
- <h4>The ORB Portability API</h4>
- <h5>Using the ORB </h5>
- <p>The ORB class provided in the package com.arjuna.orbportability.ORB shown below
- provides a uniform way of using the ORB. There are methods for obtaining a reference
- to the ORB, and for placing the application into a mode where it listens for
- incoming connections. There are also methods for registering application specific
- classes to be invoked before or after ORB initialisation. </p>
-<pre>
-public class ORB
-{
- public static ORB getInstance(String uniqueId);
- // given the various parameters,this method initialises the ORB and
- // retains a reference to it within the ORB class.
- public synchronized void initORB () throws SystemException;
- public synchronized void initORB (Applet a, Properties p)
- throws SystemException;
- public synchronized void initORB (String[] s, Properties p)
- throws SystemException;
-
- //The orb method returns a reference to the ORB.
- //After shutdown is called this reference may be null.
- public synchronized org.omg.CORBA.ORB orb ();
- public synchronized boolean setOrb (org.omg.CORBA.ORB theORB);
- // If supported, this method cleanly shuts down the ORB.
- // Any pre- and post- ORB shutdown classes which
- //have been registered will also be called.
- public synchronized void shutdown ();
-
- public synchronized boolean addAttribute (Attribute p);
- public synchronized void addPreShutdown (PreShutdown c);
- public synchronized void addPostShutdown (PostShutdown c);
-
- public synchronized void destroy () throws SystemException;
- //these methods place the ORB into a listening mode,
- //where it waits for incoming invocations.
- public void run ();
- public void run (String name);
-};
-</pre>
- <p>Note, some of the methods are not supported on all ORBs, and in this situation,
- a suitable exception will be thrown. The ORB class is a factory class which
- has no public constructor. To create an instance of an ORB you must call the
- getInstance method passing a unique name as a parameter. If this unique name
- has not been passed in a previous call to getInstance you will be returned a
- new ORB instance. Two invocations of getInstance made with the same unique name,
- within the same JVM, will return the same ORB instance. </p>
- <h5>Using the Object Adapater (OA)</h5>
- <p>The OA classes shown below provide a uniform way of using Object Adapters (OA).
- There are methods for obtaining a reference to the OA. There are also methods
- for registering application specific classes to be invoked before or after OA
- initialisation. Note, some of the methods are not supported on all ORBs, and
- in this situation, a suitable exception will be thrown. The OA class is an abstract
- class and provides the basic interface to an Object Adapter. It has two sub-classes
- RootOA and ChildOA, these classes expose the interfaces specific to the root
- Object Adapter and a child Object Adapter respectively. From the RootOA you
- can obtain a reference to the RootOA for a given ORB by using the static method
- getRootOA. To create a ChildOA instance use the createPOA method on the RootOA.</p>
- <p>As described below, the OA class and its sub-classes provide most operations
- provided by the POA as specified in the POA specification. </p>
-<pre>
-public abstract class OA
-{
- public synchronized static RootOA getRootOA(ORB associatedORB);
- public synchronized void initPOA () throws SystemException;
- public synchronized void initPOA (String[] args) throws SystemException;
- public synchronized void initOA () throws SystemException;
- public synchronized void initOA (String[] args) throws SystemException;
- public synchronized ChildOA createPOA (String adapterName,
- PolicyList policies) throws AdapterAlreadyExists, InvalidPolicy;
- public synchronized org.omg.PortableServer.POA rootPoa ();
- public synchronized boolean setPoa (org.omg.PortableServer.POA thePOA);
- public synchronized org.omg.PortableServer.POA poa (String adapterName);
- public synchronized boolean setPoa (String adapterName,
- org.omg.PortableServer.POA thePOA);
- ...
-};
-
-public class RootOA extends OA
-{
- public synchronized void destroy() throws SystemException;
- public org.omg.CORBA.Object corbaReference (Servant obj);
- public boolean objectIsReady (Servant obj, byte[] id);
- public boolean objectIsReady (Servant obj);
- public boolean shutdownObject (org.omg.CORBA.Object obj);
- public boolean shutdownObject (Servant obj);
-};
-
-public class ChildOA extends OA
-{
- public synchronized boolean setRootPoa (POA thePOA);
- public synchronized void destroy() throws SystemException;
- public org.omg.CORBA.Object corbaReference (Servant obj);
- public boolean objectIsReady (Servant obj, byte[] id)
- throws SystemException;
- public boolean objectIsReady (Servant obj) throws SystemException;
- public boolean shutdownObject (org.omg.CORBA.Object obj);
- public boolean shutdownObject (Servant obj);
-};
-</pre>
- <h5>Example</h5>
- <p>The following example illustrates how to use the ORB Portability API to create
-</p>
- <pre>
-import com.arjuna.orbportability.ORB;
-import com.arjuna.orbportability.OA;
-
-public static void main(String[] args)
-{
- try
- {
- // Create an ORB instance
- ORB orb = ORB.getInstance("orb_test");
- OA oa = OA.getRootOA( orb ); // Get the root POA
- orb.initORB(args, null); // Initialize the ORB
- oa.initOA(args); // Initialize the OA
- // Do Work
- oa.destroy(); // destroy the OA
- orb.shutdown(); // Shutdown the ORB
- }
- catch(Exception e) {}
-};
-</pre>
- <h5>Specifying the ORB to use</h5>
- <p> If using such a JDK (from its version 1.2.2) in conjunction with another ORB
- it is necessary to tell the JVM which ORB to use. This happens by specifying
- the <font face="Courier New, Courier, mono">org.omg.CORBA.ORBClass</font> and
- <font face="Courier New, Courier, mono">org.omg.CORBA.ORBSingletonClass properties</font>.
- If used, ORB Portability classes will ensure that these properties are automatically
- set when required, i.e., during ORB initialisation. </p>
- <p>The ORB portability library attempts to detect which ORB is in use, it does
- this by looking for the ORB implementation class for each ORB it supports. This
- means that if there are classes for more than one ORB in the classpath the wrong
- ORB can be detected. Therefore it is best to only have one ORB in your classpath.
- If it is necessary to have multiple ORBs in the classpath then the property
- <font face="Courier New, Courier, mono">com.hp.mw.orbportability.orbImplementation</font>
- must be set to the value specified in the table below.</p>
- <table width="75%" border="1">
- <tr bgcolor="#8BD5FC">
- <td width="22%">
- <strong>ORB</strong>
- </td>
- <td width="78%">
- <strong>Property Value</strong>
- </td>
- </tr>
- <tr>
- <td>IONA Orbix 2000 v2.0</td>
- <td>com.arjuna.orbportability.internal.orbspecific.orbix2000.orb.implementations.orbix2000_2_0</td>
- </tr>
- <tr>
- <td>HP-ORB v1.2</td>
- <td>com.arjuna.orbportability.internal.orbspecific.hporb.orb.implementations.hporb_1_2</td>
- </tr>
- <tr>
- <td>JacORB v2.0</td>
- <td>com.arjuna.orbportability.internal.orbspecific.jacorb.orb.implementations.jacorb_2_0</td>
- </tr>
- </table>
- <p>For additional details on the features provided by the ORB Portability API
- refer to the documentation provided by the ArjunaTS distribution.</p>
- <p/>
- </html>
- </area>
- </content>
- <footer/>
-</page>
Deleted: labs/jbosstm/trunk/ArjunaJTS/trailmap/docs/ArjunaTS_Recovery.xml
===================================================================
--- labs/jbosstm/trunk/ArjunaJTS/trailmap/docs/ArjunaTS_Recovery.xml 2006-09-24 05:52:34 UTC (rev 6395)
+++ labs/jbosstm/trunk/ArjunaJTS/trailmap/docs/ArjunaTS_Recovery.xml 2006-09-24 07:16:18 UTC (rev 6396)
@@ -1,334 +0,0 @@
-<?xml version="1.0"?>
-<!--
- JBoss, Home of Professional Open Source
- Copyright 2006, JBoss Inc., and individual contributors as indicated
- by the @authors tag. All rights reserved.
- See the copyright.txt in the distribution for a full listing
- of individual contributors.
- This copyrighted material is made available to anyone wishing to use,
- modify, copy, or redistribute it subject to the terms and conditions
- of the GNU General Public License, v. 2.0.
- This program is distributed in the hope that it will be useful, but WITHOUT A
- WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS FOR A
- PARTICULAR PURPOSE. See the GNU General Public License for more details.
- You should have received a copy of the GNU General Public License,
- v. 2.0 along with this distribution; if not, write to the Free Software
- Foundation, Inc., 51 Franklin Street, Fifth Floor, Boston,
- MA 02110-1301, USA.
-
- (C) 2005-2006,
- @author JBoss Inc.
--->
-<page title="Arjuna Technologies Limited: Trail map: ArjunaTS Failure Recovery" rootpath="../..">
- <header>
- Trail map: ArjunaTS - Failure Recovery
- </header>
- <content>
- <navigation>
- <links include="includes/www_arjuna_com_navigation.xml"/>
- <links include="includes/trailmap_navigation.xml"/>
- <links title="Navigation">
- <link ref="index.html">Home</link>
- </links>
- <links include="includes/trailmap_additional.xml"/>
- </navigation>
- <area title="ArjunaTS Failure Recovery">
- <html>
- <p>The failure recovery subsystem of ArjunaTS will ensure that results of
-a transaction are applied consistently to all resources affected by the
-transaction, even if any of the application processes or the machine hosting
-them crash or lose network connectivity. In the case of machine (system)
-crash or network failure, the recovery will not take place until the system
-or network are restored, but the original application does not need to
-be restarted recovery responsibility is delegated to the Recovery Manager
-process (see below). Recovery after failure requires that information about
-the transaction and the resources involved survives the failure and is
-accessible afterward: this information is held in the ActionStore, which
-is part of the ObjectStore. If the ObjectStore is destroyed or modified,
-recovery may not be possible.
-<br>Until the recovery procedures are complete, resources affected by a
-transaction that was in progress at the time of the failure may be inaccessible.
-For database resources, this may be reported as tables or rows held by
-"in-doubt transactions". </br>
- </p>
- <h4>The Recovery Manager</h4>
-The Recovery Manager is a daemon process responsible for performing crash
-recovery. Only one Recovery Manager runs per node. The Object Store provides
-persistent data storage for transactions to log data. During normal transaction
-processing each transaction will log persistent data needed for the commit
-phase to the Object Store. On successfully committing a transaction this
-data is removed, however if the transaction fails then this data remains
-within the Object Store.
-<br>The Recovery Manager functions by:</br>
- <ul>
- <li>
-Periodically scanning the Object Store for transactions that may have failed.
-Failed transactions are indicated by the presence of log data after a period
-of time that the transaction would have normally been expected to finish.</li>
- <li>
-Checking with the application process which originated the transaction
-whether the transaction is still in progress or not.</li>
- <li>
-Recovering the transaction by re-activating the transaction and then replaying
-phase two of the commit protocol.</li>
- </ul>
-To start the Recovery Manager issue the following command:
-
-<pre>
-java com.arjuna.ats.arjuna.recovery.RecoveryManager
-</pre>
-
-If the -test flag is used with the Recovery Manager then it will display a "Ready" message when initialised, i.e.,
-
-<pre>
-java com.arjuna.ats.arjuna.recovery.RecoveryManager -test
-</pre>
-
-On initialization the Recovery Manager first loads in configuration information
-via a properties file. This configuration includes a number of recovery
-activators and recovery modules, which are then dynamically loaded.
-<br>Each recovery activator, which implements the
-<font face="Courier New,Courier">com.arjuna.ats.arjuna.recovery.RecoveryActivator</font>
-interface, is used to instantiate a recovery class related to the underlying
-communication protocol. Indeed, since the version 3.0 of ArjunaTS, the
-Recovery Manager is not specifically tied to an Object Request Broker or
-ORB, which is to specify a recovery instance able to manage the OTS recovery
-protocol the new interface RecoveryActivator is provided to identify specific
-transaction protocol. For instance, when used with OTS, the RecoveryActivitor
-has the responsibility to create a RecoveryCoordinator object able to respond
-to the replay_completion operation.</br>
- <br>
-All RecoveryActivator instances inherit the same interface. They are loaded via
-the following recovery extension property:
-</br>
- <pre>
-<property
- name="com.arjuna.ats.arjuna.recovery.recoveryActivator_<number>"
- value="RecoveryClass"/>
-</pre>
- <p>For instance the RecoveryActivator provided in the distribution of JTS/OTS, which shall not be commented, is as follow : </p>
- <pre>
-<property
- name="com.arjuna.ats.arjuna.recovery.recoveryActivator_1"
- value="com.arjuna.ats.internal.jts.
- orbspecific.recovery.RecoveryEnablement"/>
-</pre>
-Each recovery module, which implements the <font face="Courier New,Courier">com.arjuna.ats.arjuna.recovery.RecoveryModule</font>
-interface, is used to recover a different type of transaction/resource,
-however each recovery module inherits the same basic behaviour.
-<br>Recovery consists of two separate passes/phases separated by two timeout
-periods. The first pass examines the object store for potentially failed
-transactions; the second pass performs crash recovery on failed transactions.
-The timeout between the first and second pass is known as the backoff period.
-The timeout between the end of the second pass and the start of the first
-pass is the recovery period. The recovery period is larger than the backoff
-period.</br>
- <br>The Recovery Manager invokes the first pass upon each recovery module,
-applies the backoff period timeout, invokes the second pass upon each recovery
-module and finally applies the recovery period timeout before restarting
-the first pass again.</br>
- <br>The recovery modules are loaded via the following recovery extension property:</br>
- <pre>
-com.arjuna.ats.arjuna.recovery.recoveryExtension<number>=<RecoveryClass>
-</pre>
-The default RecoveryExtension settings are:
-
-<pre>
-<property name="com.arjuna.ats.arjuna.recovery.recoveryExtension1"
- value="com.arjuna.ats.internal.
- arjuna.recovery.AtomicActionRecoveryModule"/>
-<property name="com.arjuna.ats.arjuna.recovery.recoveryExtension2"
- value="com.arjuna.ats.internal.
- txoj.recovery.TORecoveryModule"/>
-<property name="com.arjuna.ats.arjuna.recovery.recoveryExtension3"
- value="com.arjuna.ats.internal.
- jts.recovery.transactions.TopLevelTransactionRecoveryModule"/>
-<property name="com.arjuna.ats.arjuna.recovery.recoveryExtension4"
- value="com.arjuna.ats.internal.
- jts.recovery.transactions.ServerTransactionRecoveryModule"/>
-</pre>
- <h4>Configuring the Recovery Manager</h4>
- <h5>Periodic Recovery</h5>
-The backoff period and recovery period are set using the following properties:
-
-<pre>
-com.arjuna.ats.arjuna.recovery.recoveryBackoffPeriod (default 10 secs)
-com.arjuna.ats.arjuna.recovery.periodicRecovery (default 120 secs)
-</pre>
- <h5>Expired entry removal</h5>
-The operation of the recovery subsystem will cause some entries to be made
-in the ObjectStore that will not be removed in normal progress. The RecoveryManager
-has a facility for scanning for these and removing items that are very
-old. Scans and removals are performed by implementations of the <font face="Courier New,Courier">com.arjuna.ats.arjuna.recovery.ExpiryScanner</font>.
-Implementations of this interface are loaded by giving the class name as
-the value of a property whose name begins with <font face="Courier New,Courier">ExperyScanner</font>.
-<br>The RecoveryManager calls the scan() method on each loaded ExpiryScanner
-implementation at an interval determined by the property <font face="Courier New,Courier">com.arjuna.ats.arjuna.recovery.expiryScanInterval</font>.
-This value is given in hours default is 12. An EXPIRY_SCAN_INTERVAL value
-of zero will suppress any expiry scanning. If the value as supplied is
-positive, the first scan is performed when RecoveryManager starts; if the
-value is negative, the first scan is delayed until after the first interval
-(using the absolute value)</br>
- <br>The default ExpiryScanner is:</br>
- <pre>
-<property
- name="com.arjuna.ats.arjuna.recovery.
- expiryScannerTransactionStatusManager"
- value="com.arjuna.ats.internal.arjuna.recovery.
- ExpiredTransactionStatusManagerScanner"/>
- </pre>
- <p>The following table summarize properties used by the Recovery Manager. These
- properties are defined by default the properties file named RecoveryManager-properties.xml.
-</p>
- <table BORDER="" WIDTH="100%">
- <tr ALIGN="CENTER" BGCOLOR="#66FFFF">
- <td width="38%">
- <b>Name</b>
- </td>
- <td width="34%">
- <b>Description</b>
- </td>
- <td width="9%">
- <b>Possible Value</b>
- </td>
- <td width="19%">
- <b>Default Value</b>
- </td>
- </tr>
- <tr>
- <td>
- <font size="-7">com.arjuna.ats.arjuna.<br/>
- recovery.periodicRecoveryPeriod</font>
- </td>
- <td>
- <font size="-7">Interval in seconds between initiating the periodic recovery modules</font>
- </td>
- <td>
- <font size="-7">Value in seconds</font>
- </td>
- <td>
- <font size="-7">120</font>
- </td>
- </tr>
- <tr>
- <td>
- <font size="-7">com.arjuna.ats.arjuna.<br/>
- recovery.recoveryBackoffPeriod</font>
- </td>
- <td>
- <font size="-7">Interval in seconds between first and second pass of periodic recovery</font>
- </td>
- <td>
- <font size="-7">Value in seconds</font>
- </td>
- <td>
- <font size="-7">10</font>
- </td>
- </tr>
- <tr>
- <td>
- <font size="-7">com.arjuna.ats.arjuna.<br/>
- recovery.recoveryExtensionX</font>
- </td>
- <td>
- <font size="-7">Indicates a periodic recovery module to use. X is the occurence number
- of the recovery module among a set of recovery modules. These modules are
- invoked in sort-order of names</font>
- </td>
- <td>
- <font size="-6">The class name of the periodic recovery module </font>
- </td>
- <td>
- <font size="-8">ArjunaTS provides a set classes given in the RecoveryManager-properties.xml file</font>
- </td>
- </tr>
- <tr>
- <td>
- <font size="-7">com.arjuna.ats.arjuna.<br/>
- recovery.recoveryActivator_X</font>
- </td>
- <td>
- <font size="-7">Indicates a recovery activator to use. X is the occurence number of the
- recovery activator among a set of recovery activators. </font>
- </td>
- <td>
- <font size="-7">The class name of the periodic recovery activator</font>
- </td>
- <td>
- <font size="-7">ArjunaTS provide one class that manages the recovery protocol specified
- by the OTS specification </font>
- </td>
- </tr>
- <tr>
- <td>
- <font size="-7">com.arjuna.ats.arjuna.<br/>
- recovery.expiryScannerXXX</font>
- </td>
- <td>
- <font size="-7">Expiry scanners to use (order of invocation is random). Names must begin
- with "com.arjuna.ats.arjuna.<br/>recovery.expiryScanner"</font>
- </td>
- <td>
- <font size="-7">Class name</font>
- </td>
- <td>
- <font size="-7">ArjunaTS provides one class given in the RecoveryManager-properties.xml file</font>
- </td>
- </tr>
- <tr>
- <td>
- <font size="-7">com.arjuna.ats.arjuna.<br/>
- recovery.expiryScanInterval</font>
- </td>
- <td>
- <font size="-7">Interval, in hours, between running the expiry scanners. This can be
- quite long. The absolute value determines the interval - if the value is
- negative, the scan will NOT be run until after one interval has elapsed.
- If positive the first scan will be immediately
- after startup. Zero will prevent any scanning. </font>
- </td>
- <td>
- <font size="-7">Value in hours</font>
- </td>
- <td>
- <font size="-7">12 </font>
- </td>
- </tr>
- <tr>
- <td>
- <font size="-7">com.arjuna.ats.arjuna.recovery.<br/>
- transactionStatusManagerExpiryTime</font>
- </td>
- <td>
- <font size="-7">Age, in hours, for removal of transaction status manager item. This should
- be longer than any ts-using process will remain running. Zero = Never removed.
- </font>
- </td>
- <td>
- <font size="-7">Value in Hours</font>
- </td>
- <td>
- <font size="-7">12 </font>
- </td>
- </tr>
- <tr>
- <td>
- <font size="-7">com.arjuna.ats.arjuna.recovery<br/>
- transactionStatusManagerPort</font>
- </td>
- <td>
- <font size="-7">Use this to fix the port on which the TransactionStatusManager listens</font>
- </td>
- <td>
- <font size="-7">Port number (short) </font>
- </td>
- <td>
- <font size="-7">use a free port</font>
- </td>
- </tr>
- </table>
- </html>
- </area>
- </content>
- <footer/>
-</page>
Modified: labs/jbosstm/trunk/ArjunaJTS/trailmap/docs/DTP.xml
===================================================================
--- labs/jbosstm/trunk/ArjunaJTS/trailmap/docs/DTP.xml 2006-09-24 05:52:34 UTC (rev 6395)
+++ labs/jbosstm/trunk/ArjunaJTS/trailmap/docs/DTP.xml 2006-09-24 07:16:18 UTC (rev 6396)
@@ -331,7 +331,7 @@
environment. For this aim various distributed transaction processing
standards have been developed by international standards organizations.
Among these organizations, We list three of them which are mainly
- considered in the Arjuna Transaction Service product: </p>
+ considered in the JBoss Transaction Service product: </p>
<ul>
<li>
The <a class="linkscoloured" href="xopen_overview.html">X/Open model </a> and its successful XA interface
Copied: labs/jbosstm/trunk/ArjunaJTS/trailmap/docs/JBossTS_Configuration.xml (from rev 6394, labs/jbosstm/trunk/ArjunaJTS/trailmap/docs/ArjunaTS_Configuration.xml)
===================================================================
--- labs/jbosstm/trunk/ArjunaJTS/trailmap/docs/ArjunaTS_Configuration.xml 2006-09-23 23:04:39 UTC (rev 6394)
+++ labs/jbosstm/trunk/ArjunaJTS/trailmap/docs/JBossTS_Configuration.xml 2006-09-24 07:16:18 UTC (rev 6396)
@@ -0,0 +1,558 @@
+<?xml version="1.0"?>
+<!--
+ JBoss, Home of Professional Open Source
+ Copyright 2006, JBoss Inc., and individual contributors as indicated
+ by the @authors tag. All rights reserved.
+ See the copyright.txt in the distribution for a full listing
+ of individual contributors.
+ This copyrighted material is made available to anyone wishing to use,
+ modify, copy, or redistribute it subject to the terms and conditions
+ of the GNU General Public License, v. 2.0.
+ This program is distributed in the hope that it will be useful, but WITHOUT A
+ WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS FOR A
+ PARTICULAR PURPOSE. See the GNU General Public License for more details.
+ You should have received a copy of the GNU General Public License,
+ v. 2.0 along with this distribution; if not, write to the Free Software
+ Foundation, Inc., 51 Franklin Street, Fifth Floor, Boston,
+ MA 02110-1301, USA.
+
+ (C) 2005-2006,
+ @author JBoss Inc.
+-->
+<page title="JBoss (a Division of Redhat): Trail map: Configuring the JBoss Transaction Service" rootpath="../..">
+ <header>
+ Trail map: JBossTS Configuration
+ </header>
+ <content>
+ <navigation>
+ <links include="includes/www_arjuna_com_navigation.xml"/>
+ <links include="includes/trailmap_navigation.xml"/>
+ <links title="Navigation">
+ <link ref="index.html">Home</link>
+ </links>
+ <links include="includes/trailmap_additional.xml"/>
+ </navigation>
+ <area title="Configuring the Arjuna 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.
+ Basically, the behaviour of the JBossTS product is configurable through property
+ attributes. Although these property attributes may be specified as command line
+ 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
+ </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>
+<pre>
+<property>
+ name="a_name"
+ value="a_value"
+</property>
+</pre>
+</blockquote>
+
+<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>
+ <ul>
+ <li>
+ <b>Name</b> : indicates the name of the property</li>
+ <li>
+ <b>Description</b>: explain the aim of the property</li>
+ <li>
+ <b>Possible Value</b>: indicates possible value the property can have</li>
+ <li>
+ <b>Default</b>
+ <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%">
+ <b>Name</b>
+ </td>
+ <td width="25%">
+ <b>Description</b>
+ </td>
+ <td width="10%">
+ <b>Possible Value</b>
+ </td>
+ <td width="27%">
+ <b>Default Value</b>
+ </td>
+ </tr>
+
+ <tr>
+ <td>com.arjuna.ats.arjuna.<br/>objectstore.localOSRoot</td>
+ <td>By default, all object states will be stored within the "defaultStore"
+ subdirectory of the object store root. However, this subdirectory can be
+ changed by setting the localOSRoot property variable accordingly</td>
+ <td>Directory name</td>
+ <td>defaultStore</td>
+ </tr>
+ <tr>
+ <td>com.arjuna.ats.arjuna.<br/>objectstore.objectStoreDir</td>
+ <td>Specify the location of the ObjectStore</td>
+ <td>Directory name</td>
+ <td>PutObjectStoreDirHere</td>
+ </tr>
+ <tr>
+ <td>com.arjuna.ats.arjuna.common.varDir</td>
+ <td>JBossTS needs to be able to write temporary files to a well known location
+ during execution. By default this location is var. However, by setting the
+ varDir property variable this can be overridden.</td>
+ <td>Directory name</td>
+ <td>var/tmp</td>
+ </tr>
+ </table>
+ <h4>ObjectStore management</h4>
+The JBossTS layer requires an object store for transaction management <a class="linkscoloured" href="DTP.html#RecoveryLog">logs</a>. Within
+the transaction service installation, object store is updated regularly whenever
+transactions are created, or when Transactional Objects for Java is used. In a
+failure free environment, the only object states which should reside within the
+object store are those representing objects created with the Transactional Objects
+for Java API. However, if failures occur, transaction logs may remain in the object
+store until crash recovery facilities have resolved the transactions they represent.
+As such it is very important that the contents of the object store are not deleted
+without due care and attention, as this will make it impossible to resolve in
+doubt transactions. In addition, if multiple users share the same object store
+it is important that they realise this and do not simply delete the contents of
+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
+ during the JBossTS installation. At any time, the location of the ObjectStore
+ may be changed.</p>
+ <h4>Configuring Output</h4>
+ <p>Sometimes it is desirable, mainly in case of debugging, to have some form of
+ output during execution to trace internal actions performed. JBossTS uses the
+ logging tracing mechanism provided by the Arjuna Common Logging Framework (CLF)
+ version 2.4, which provides a high level interface that hides differences that
+ exist between logging APIs such Jakarta log4j, JDK 1.4 logging API or dotnet
+ logging API.</p>
+ <p>With the CLF applications make logging calls on commonLogger objects. These
+ commonLogger objects pass log messages to Handler for publication. Both commonLoggers
+ and Handlers may use logging Levels to decide if they are interested in a particular
+ log message. Each log message has an associated log Level, that gives the importance
+ and urgency of a log message. The set of possible Log Levels are DEBUG, INFO,
+ WARN, ERROR and FATAL. Defined Levels are ordered according to their integer
+ values as follows: DEBUG < INFO < WARN < ERROR < FATAL. </p>
+ <p> The CLF provides an extension to filter logging messages according to finer
+ granularity an application may define. That is, when a log message is provided
+ to the commonLogger with the DEBUG level, additional conditions can be specified
+ to determine if the log message is enabled or not. <br/>
+ <b>Note</b>: These conditions are applied if and only the DEBUG level is enabled
+ and the log request performed by the application specifies debugging granularity.
+ <br/>
+ When enabled, Debugging is filtered conditionally on three variables: </p>
+ <ul>
+ <li> Debugging level: this is where the log request with the DEBUG Level is
+ generated from, e.g., constructors or basic methods.</li>
+ <li> Visibility level: the visibility of the constructor, method, etc. that
+ generates the debugging.</li>
+ <li> Facility code: for instance the package or sub-module within which debugging
+ is generated, e.g., the object store.</li>
+ </ul>
+ <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
+ 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:
+</p>
+ <ul>
+ <li>Debugging level – JBossTS uses the default values defined in the class
+ com.arjuna.common.util.logging.CommonDebugLevel </li>
+ </ul>
+ <table width="83%" border="1">
+ <tr bgcolor="#8BD5FC">
+ <td width="33%">
+ <div align="center">
+ <strong>Debug Level</strong>
+ </div>
+ </td>
+ <td width="24%">
+ <div align="center">
+ <strong>Value</strong>
+ </div>
+ </td>
+ <td width="43%">
+ <div align="center">
+ <strong>Description</strong>
+ </div>
+ </td>
+ </tr>
+ <tr>
+ <td>NO_DEBUGGING</td>
+ <td>
+ <font face="Courier New, Courier, mono">0x0000</font>
+ </td>
+ <td>A commonLogger object assigned with this values discard all debug requests</td>
+ </tr>
+ <tr>
+ <td>CONSTRUCTORS</td>
+ <td>
+ <font face="Courier New, Courier, mono"> 0x0001</font>
+ </td>
+ <td>Diagnostics from constructors</td>
+ </tr>
+ <tr>
+ <td>DESTRUCTORS</td>
+ <td>
+ <font face="Courier New, Courier, mono">0x0002</font>
+ </td>
+ <td>Diagnostics from finalizers.</td>
+ </tr>
+ <tr>
+ <td>CONSTRUCT_AND_DESTRUCT</td>
+ <td>
+ <font face="Courier New, Courier, mono">CONSTRUCTORS | DESTRUCTORS</font>
+ </td>
+ <td>Diagnostics from constructors and finalizers</td>
+ </tr>
+ <tr>
+ <td>FUNCTIONS</td>
+ <td>
+ <font face="Courier New, Courier, mono">0x010</font>
+ </td>
+ <td>Diagnostics from functions</td>
+ </tr>
+ <tr>
+ <td>OPERATORS</td>
+ <td>
+ <font face="Courier New, Courier, mono">0x020</font>
+ </td>
+ <td>Diagnostics from operators, such as equals</td>
+ </tr>
+ <tr>
+ <td>FUNCS_AND_OPS</td>
+ <td>
+ <font face="Courier New, Courier, mono">FUNCTIONS | OPERATORS</font>
+ </td>
+ <td>Diagnostics from functions and operations.</td>
+ </tr>
+ <tr>
+ <td>ALL_NON_TRIVIAL</td>
+ <td>
+ <font face="Courier New, Courier, mono">CONSTRUCT_AND_DESTRUCT | FUNCTIONS
+ | OPERATORS</font>
+ </td>
+ <td>Diagnostics from all non-trivial operations</td>
+ </tr>
+ <tr>
+ <td>TRIVIAL_FUNCS</td>
+ <td>
+ <font face="Courier New, Courier, mono">0x0100</font>
+ </td>
+ <td>Diagnostics from trivial functions.</td>
+ </tr>
+ <tr>
+ <td>TRIVIAL_OPERATORS:</td>
+ <td>
+ <font face="Courier New, Courier, mono">0x0200</font>
+ </td>
+ <td>Diagnostics from trivial operations, and operators.</td>
+ </tr>
+ <tr>
+ <td> ALL_TRIVIAL</td>
+ <td>
+ <font face="Courier New, Courier, mono">TRIVIAL_FUNCS | TRIVIAL_OPERATORS</font>
+ </td>
+ <td>Diagnostics from all trivial operations</td>
+ </tr>
+ <tr>
+ <td>FULL_DEBUGGING</td>
+ <td>
+ <font face="Courier New, Courier, mono">0xffff</font>
+ </td>
+ <td>Full diagnostics.</td>
+ </tr>
+ </table>
+ <ul>
+ <li>Visibility level – JBossTS uses the default values defined in the class
+ com.arjuna.common.util.logging.CommonVisibilityLevel </li>
+ </ul>
+ <table width="83%" border="1">
+ <tr bgcolor="#8BD5FC">
+ <td width="33%">
+ <div align="center">
+ <strong>Debug Level</strong>
+ </div>
+ </td>
+ <td width="24%">
+ <div align="center">
+ <strong>Value</strong>
+ </div>
+ </td>
+ <td width="43%">
+ <div align="center">
+ <strong>Description</strong>
+ </div>
+ </td>
+ </tr>
+ <tr>
+ <td>VIS_NONE</td>
+ <td>
+ <font face="Courier New, Courier, mono">0x0000</font>
+ </td>
+ <td>No Diagnostic</td>
+ </tr>
+ <tr>
+ <td>VIS_PRIVATE</td>
+ <td>
+ <font face="Courier New, Courier, mono">0x0001</font>
+ </td>
+ <td>only from private methods.</td>
+ </tr>
+ <tr>
+ <td>VIS_PROTECTED</td>
+ <td>
+ <font face="Courier New, Courier, mono">0x0002</font>
+ </td>
+ <td>only from protected methods.</td>
+ </tr>
+ <tr>
+ <td>VIS_PUBLIC</td>
+ <td>
+ <font face="Courier New, Courier, mono">0x0004</font>
+ </td>
+ <td>only from public methods.</td>
+ </tr>
+ <tr>
+ <td>VIS_PACKAGE</td>
+ <td>
+ <font face="Courier New, Courier, mono">0x0008</font>
+ </td>
+ <td>only from package methods.</td>
+ </tr>
+ <tr>
+ <td>VIS_ALL</td>
+ <td>
+ <font face="Courier New, Courier, mono">0xffff</font>
+ </td>
+ <td>Full Diagnostic</td>
+ </tr>
+ </table>
+ <ul>
+ <li>Facility Code – JBossTS uses the following values </li>
+ </ul>
+ <table width="83%" border="1">
+ <tr bgcolor="#8BD5FC">
+ <td>
+ <div align="center">
+ <strong>Facility Code Level </strong>
+ </div>
+ </td>
+ <td>
+ <div align="center">
+ <strong>Value</strong>
+ </div>
+ </td>
+ <td>
+ <div align="center">
+ <strong>Description</strong>
+ </div>
+ </td>
+ </tr>
+ <tr>
+ <td>FAC_ATOMIC_ACTION</td>
+ <td>
+ <font face="Courier New, Courier, mono">0x00000001</font>
+ </td>
+ <td>atomic action core module</td>
+ </tr>
+ <tr>
+ <td>FAC_BUFFER_MAN</td>
+ <td>
+ <font face="Courier New, Courier, mono">0x00000004</font>
+ </td>
+ <td>state management (buffer) classes</td>
+ </tr>
+ <tr>
+ <td>FAC_ABSTRACT_REC</td>
+ <td>
+ <font face="Courier New, Courier, mono">0x00000008</font>
+ </td>
+ <td>abstract records</td>
+ </tr>
+ <tr>
+ <td>FAC_OBJECT_STORE</td>
+ <td>
+ <font face="Courier New, Courier, mono">0x00000010</font>
+ </td>
+ <td>object store implementations</td>
+ </tr>
+ <tr>
+ <td> FAC_STATE_MAN</td>
+ <td>
+ <font face="Courier New, Courier, mono">0x00000020</font>
+ </td>
+ <td>state management and StateManager)</td>
+ </tr>
+ <tr>
+ <td>FAC_SHMEM</td>
+ <td>
+ <font face="Courier New, Courier, mono">0x00000040 </font>
+ </td>
+ <td>shared memory implementation classes</td>
+ </tr>
+ <tr>
+ <td>FAC_GENERAL</td>
+ <td>
+ <font face="Courier New, Courier, mono">0x00000080</font>
+ </td>
+ <td>general classes</td>
+ </tr>
+ <tr>
+ <td>FAC_CRASH_RECOVERY</td>
+ <td>
+ <font face="Courier New, Courier, mono">0x00000800</font>
+ </td>
+ <td>detailed trace of crash recovery module and classes</td>
+ </tr>
+ <tr>
+ <td>FAC_THREADING</td>
+ <td>
+ <font face="Courier New, Courier, mono">0x00002000</font>
+ </td>
+ <td>threading classes</td>
+ </tr>
+ <tr>
+ <td>FAC_JDBC</td>
+ <td>
+ <font face="Courier New, Courier, mono">0x00008000</font>
+ </td>
+ <td>JDBC 1.0 and 2.0 support</td>
+ </tr>
+ <tr>
+ <td>FAC_RECOVERY_NORMAL</td>
+ <td>
+ <font face="Courier New, Courier, mono">0x00040000</font>
+ </td>
+ <td>normal output for crash recovery manager</td>
+ </tr>
+ </table>
+ <p>To ensure appropriate output, it is necessary to set some of the finer debug
+ properties explicitly as follows:</p>
+ <pre> <properties>
+ <!-- CLF 2.4 properties -->
+ <property
+ name="com.arjuna.common.util.logging.DebugLevel"
+ value="0x00000000"/>
+ <property
+ name="com.arjuna.common.util.logging.FacilityLevel"
+ value="0xffffffff"/>
+ <property
+ name="com.arjuna.common.util.logging.VisibilityLevel"
+ value="0xffffffff"/>
+ <property
+ name="com.arjuna.common.util.logger"
+ value="log4j"/>
+ </properties></pre>
+ <p>By default, debugging messages are not enabled since the DebugLevel is set
+ to NO_DEBUGGING (<font face="Courier New, Courier, mono">0x00000000</font>).
+ You can enable debugging by providing one of the appropriate value listed above
+ - for instance with you wish to see all internal actions performed by the RecoveryManager
+ to recover transactions from a failure set the DebugLevel to FULL_DEBUGGING
+ (<font face="Courier New, Courier, mono">0xffffffff</font>) and the FacilityCode
+ Level FAC_CRASH_RECOVERY. </p>
+ <p>
+ <strong>Note</strong>: To enable finger debug messages, the logging level should
+ be set to the DEBUG level as described below.</p>
+ <p>From the program point of view a same API is used whatever the underlying logging
+ mechanism, but from a configuration point of view is that the user is totally
+ responsible for the configuration of the underlying logging system. Hence, the
+ properties of the underlying log system are configured in a manner specific
+ to that log system, e.g., a log4j.properties file in the case that log4j logging
+ is used. To set the logging level to the DEBUG value, the log4j.properties file
+ can be edited to set that value. </p>
+ <p>The property <font face="Courier New, Courier, mono">com.arjuna.common.util.logger</font>
+ allows to select the underlying logging system. Possible value are listed in
+ the following table.</p>
+ <table width="93%" border="1">
+ <tr bgcolor="#8BD5FC">
+ <td width="14%">
+ <div align="center">
+ <strong>Property Value</strong>
+ </div>
+ </td>
+ <td width="86%">
+ <div align="center">
+ <strong>Description</strong>
+ </div>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ <font face="Courier New, Courier, mono">log4j</font>
+ </td>
+ <td>Log4j logging (log4j classes must be available in the classpath); configuration
+ through the log4j.properties file, which is picked up from the CLASSPATH
+ or given through a System property: <font face="Courier New, Courier, mono">log4j.configuration</font>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ <font face="Courier New, Courier, mono">jdk14</font>
+ </td>
+ <td>JDK 1.4 logging API (only supported on JVMs of version 1.4 or higher).
+ Configuration is done through a file logging.properties in the jre/lib directory.</td>
+ </tr>
+ <tr>
+ <td>
+ <font face="Courier New, Courier, mono">simple</font>
+ </td>
+ <td>Selects the simple JDK 1.1 compatible console-based logger provided by
+ Jakarta Commons Logging</td>
+ </tr>
+ <tr>
+ <td>
+ <font face="Courier New, Courier, mono">csf</font>
+ </td>
+ <td>Selects CSF-based logging (CSF embeddor must be available)</td>
+ </tr>
+ <tr>
+ <td>
+ <font face="Courier New, Courier, mono">jakarta</font>
+ </td>
+ <td>Uses the default log system selection algorithm of the Jakarta Commons
+ Logging framework</td>
+ </tr>
+ <tr>
+ <td>
+ <font face="Courier New, Courier, mono">dotnet</font>
+ </td>
+ <td>Selects a .net logging implementation <br/>
+ Since a dotnet logger is not currently implemented, this is currently identical
+ to <font face="Courier New, Courier, mono">simple</font>. Simple is a purely
+ JDK1.1 console-based log implementation.</td>
+ </tr>
+ <tr>
+ <td>
+ <font face="Courier New, Courier, mono">avalon</font>
+ </td>
+ <td>Uses the Avalon Logkit implementation</td>
+ </tr>
+ <tr>
+ <td>
+ <font face="Courier New, Courier, mono">noop</font>
+ </td>
+ <td>Disables all logging </td>
+ </tr>
+ </table>
+ </html>
+ </area>
+ </content>
+ <footer/>
+</page>
Copied: labs/jbosstm/trunk/ArjunaJTS/trailmap/docs/JBossTS_ORBPortability.xml (from rev 6394, labs/jbosstm/trunk/ArjunaJTS/trailmap/docs/ArjunaTS_ORBPortability.xml)
===================================================================
--- labs/jbosstm/trunk/ArjunaJTS/trailmap/docs/ArjunaTS_ORBPortability.xml 2006-09-23 23:04:39 UTC (rev 6394)
+++ labs/jbosstm/trunk/ArjunaJTS/trailmap/docs/JBossTS_ORBPortability.xml 2006-09-24 07:16:18 UTC (rev 6396)
@@ -0,0 +1,218 @@
+<?xml version="1.0"?>
+<!--
+ JBoss, Home of Professional Open Source
+ Copyright 2006, JBoss Inc., and individual contributors as indicated
+ by the @authors tag. All rights reserved.
+ See the copyright.txt in the distribution for a full listing
+ of individual contributors.
+ This copyrighted material is made available to anyone wishing to use,
+ modify, copy, or redistribute it subject to the terms and conditions
+ of the GNU General Public License, v. 2.0.
+ This program is distributed in the hope that it will be useful, but WITHOUT A
+ WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS FOR A
+ PARTICULAR PURPOSE. See the GNU General Public License for more details.
+ You should have received a copy of the GNU General Public License,
+ v. 2.0 along with this distribution; if not, write to the Free Software
+ Foundation, Inc., 51 Franklin Street, Fifth Floor, Boston,
+ MA 02110-1301, USA.
+
+ (C) 2005-2006,
+ @author JBoss Inc.
+-->
+<page title="JBoss (a Division of Redhat): Trail map: ORB Portability" rootpath="../..">
+ <header> Trail map: ORB Portability </header>
+ <content>
+ <navigation>
+ <links include="includes/www_arjuna_com_navigation.xml"/>
+ <links include="includes/trailmap_navigation.xml"/>
+ <links title="Navigation">
+ <link ref="index.html">Home</link>
+ </links>
+ <links include="includes/trailmap_additional.xml"/>
+ </navigation>
+ <area title="ORB Portability">
+ <html>
+ <h4>Introduction</h4>
+ <p>Many ORBs currently in use support different versions of CORBA and/or the Java
+ language mapping.<br>
+ The JBoss Transaction Service only supports the new Portable Object Adapter
+ (POA) architecture described in the CORBA 2.3 specification as a replacement
+ for the Basic Object Adapter (BOA). Unlike the BOA, which was weakly specified
+ and led to a number of different (and often conflicting) implementations, the
+ POA was deliberately designed to reduce the differences between ORB implementations,
+ and thus minimise the amount of re-coding that would need to be done when porting
+ applications from one ORB to another. However, there is still scope for slight
+ differences between ORB implementations, notably in the area of threading. Note,
+ instead of talking about the POA, this manual will consider the Object Adapter</br>
+ (OA).</p>
+ <p>Because the Arjuna Transaction Service must be able to run on a number of different
+ ORBs, we have developed an ORB portability interface which allows entire applications
+ to be moved between ORBs with little or no modifications. This portability interface
+ is available to the application programmer in the form of several Java classes.
+</p>
+ <h4>The ORB Portability API</h4>
+ <h5>Using the ORB </h5>
+ <p>The ORB class provided in the package com.arjuna.orbportability.ORB shown below
+ provides a uniform way of using the ORB. There are methods for obtaining a reference
+ to the ORB, and for placing the application into a mode where it listens for
+ incoming connections. There are also methods for registering application specific
+ classes to be invoked before or after ORB initialisation. </p>
+<pre>
+public class ORB
+{
+ public static ORB getInstance(String uniqueId);
+ // given the various parameters,this method initialises the ORB and
+ // retains a reference to it within the ORB class.
+ public synchronized void initORB () throws SystemException;
+ public synchronized void initORB (Applet a, Properties p)
+ throws SystemException;
+ public synchronized void initORB (String[] s, Properties p)
+ throws SystemException;
+
+ //The orb method returns a reference to the ORB.
+ //After shutdown is called this reference may be null.
+ public synchronized org.omg.CORBA.ORB orb ();
+ public synchronized boolean setOrb (org.omg.CORBA.ORB theORB);
+ // If supported, this method cleanly shuts down the ORB.
+ // Any pre- and post- ORB shutdown classes which
+ //have been registered will also be called.
+ public synchronized void shutdown ();
+
+ public synchronized boolean addAttribute (Attribute p);
+ public synchronized void addPreShutdown (PreShutdown c);
+ public synchronized void addPostShutdown (PostShutdown c);
+
+ public synchronized void destroy () throws SystemException;
+ //these methods place the ORB into a listening mode,
+ //where it waits for incoming invocations.
+ public void run ();
+ public void run (String name);
+};
+</pre>
+ <p>Note, some of the methods are not supported on all ORBs, and in this situation,
+ a suitable exception will be thrown. The ORB class is a factory class which
+ has no public constructor. To create an instance of an ORB you must call the
+ getInstance method passing a unique name as a parameter. If this unique name
+ has not been passed in a previous call to getInstance you will be returned a
+ new ORB instance. Two invocations of getInstance made with the same unique name,
+ within the same JVM, will return the same ORB instance. </p>
+ <h5>Using the Object Adapater (OA)</h5>
+ <p>The OA classes shown below provide a uniform way of using Object Adapters (OA).
+ There are methods for obtaining a reference to the OA. There are also methods
+ for registering application specific classes to be invoked before or after OA
+ initialisation. Note, some of the methods are not supported on all ORBs, and
+ in this situation, a suitable exception will be thrown. The OA class is an abstract
+ class and provides the basic interface to an Object Adapter. It has two sub-classes
+ RootOA and ChildOA, these classes expose the interfaces specific to the root
+ Object Adapter and a child Object Adapter respectively. From the RootOA you
+ can obtain a reference to the RootOA for a given ORB by using the static method
+ getRootOA. To create a ChildOA instance use the createPOA method on the RootOA.</p>
+ <p>As described below, the OA class and its sub-classes provide most operations
+ provided by the POA as specified in the POA specification. </p>
+<pre>
+public abstract class OA
+{
+ public synchronized static RootOA getRootOA(ORB associatedORB);
+ public synchronized void initPOA () throws SystemException;
+ public synchronized void initPOA (String[] args) throws SystemException;
+ public synchronized void initOA () throws SystemException;
+ public synchronized void initOA (String[] args) throws SystemException;
+ public synchronized ChildOA createPOA (String adapterName,
+ PolicyList policies) throws AdapterAlreadyExists, InvalidPolicy;
+ public synchronized org.omg.PortableServer.POA rootPoa ();
+ public synchronized boolean setPoa (org.omg.PortableServer.POA thePOA);
+ public synchronized org.omg.PortableServer.POA poa (String adapterName);
+ public synchronized boolean setPoa (String adapterName,
+ org.omg.PortableServer.POA thePOA);
+ ...
+};
+
+public class RootOA extends OA
+{
+ public synchronized void destroy() throws SystemException;
+ public org.omg.CORBA.Object corbaReference (Servant obj);
+ public boolean objectIsReady (Servant obj, byte[] id);
+ public boolean objectIsReady (Servant obj);
+ public boolean shutdownObject (org.omg.CORBA.Object obj);
+ public boolean shutdownObject (Servant obj);
+};
+
+public class ChildOA extends OA
+{
+ public synchronized boolean setRootPoa (POA thePOA);
+ public synchronized void destroy() throws SystemException;
+ public org.omg.CORBA.Object corbaReference (Servant obj);
+ public boolean objectIsReady (Servant obj, byte[] id)
+ throws SystemException;
+ public boolean objectIsReady (Servant obj) throws SystemException;
+ public boolean shutdownObject (org.omg.CORBA.Object obj);
+ public boolean shutdownObject (Servant obj);
+};
+</pre>
+ <h5>Example</h5>
+ <p>The following example illustrates how to use the ORB Portability API to create
+</p>
+ <pre>
+import com.arjuna.orbportability.ORB;
+import com.arjuna.orbportability.OA;
+
+public static void main(String[] args)
+{
+ try
+ {
+ // Create an ORB instance
+ ORB orb = ORB.getInstance("orb_test");
+ OA oa = OA.getRootOA( orb ); // Get the root POA
+ orb.initORB(args, null); // Initialize the ORB
+ oa.initOA(args); // Initialize the OA
+ // Do Work
+ oa.destroy(); // destroy the OA
+ orb.shutdown(); // Shutdown the ORB
+ }
+ catch(Exception e) {}
+};
+</pre>
+ <h5>Specifying the ORB to use</h5>
+ <p> If using such a JDK (from its version 1.2.2) in conjunction with another ORB
+ it is necessary to tell the JVM which ORB to use. This happens by specifying
+ the <font face="Courier New, Courier, mono">org.omg.CORBA.ORBClass</font> and
+ <font face="Courier New, Courier, mono">org.omg.CORBA.ORBSingletonClass properties</font>.
+ If used, ORB Portability classes will ensure that these properties are automatically
+ set when required, i.e., during ORB initialisation. </p>
+ <p>The ORB portability library attempts to detect which ORB is in use, it does
+ this by looking for the ORB implementation class for each ORB it supports. This
+ means that if there are classes for more than one ORB in the classpath the wrong
+ ORB can be detected. Therefore it is best to only have one ORB in your classpath.
+ If it is necessary to have multiple ORBs in the classpath then the property
+ <font face="Courier New, Courier, mono">com.hp.mw.orbportability.orbImplementation</font>
+ must be set to the value specified in the table below.</p>
+ <table width="75%" border="1">
+ <tr bgcolor="#8BD5FC">
+ <td width="22%">
+ <strong>ORB</strong>
+ </td>
+ <td width="78%">
+ <strong>Property Value</strong>
+ </td>
+ </tr>
+ <tr>
+ <td>IONA Orbix 2000 v2.0</td>
+ <td>com.arjuna.orbportability.internal.orbspecific.orbix2000.orb.implementations.orbix2000_2_0</td>
+ </tr>
+ <tr>
+ <td>HP-ORB v1.2</td>
+ <td>com.arjuna.orbportability.internal.orbspecific.hporb.orb.implementations.hporb_1_2</td>
+ </tr>
+ <tr>
+ <td>JacORB v2.0</td>
+ <td>com.arjuna.orbportability.internal.orbspecific.jacorb.orb.implementations.jacorb_2_0</td>
+ </tr>
+ </table>
+ <p>For additional details on the features provided by the ORB Portability API
+ refer to the documentation provided by the JBossTS distribution.</p>
+ <p/>
+ </html>
+ </area>
+ </content>
+ <footer/>
+</page>
Copied: labs/jbosstm/trunk/ArjunaJTS/trailmap/docs/JBossTS_Recovery.xml (from rev 6394, labs/jbosstm/trunk/ArjunaJTS/trailmap/docs/ArjunaTS_Recovery.xml)
===================================================================
--- labs/jbosstm/trunk/ArjunaJTS/trailmap/docs/ArjunaTS_Recovery.xml 2006-09-23 23:04:39 UTC (rev 6394)
+++ labs/jbosstm/trunk/ArjunaJTS/trailmap/docs/JBossTS_Recovery.xml 2006-09-24 07:16:18 UTC (rev 6396)
@@ -0,0 +1,334 @@
+<?xml version="1.0"?>
+<!--
+ JBoss, Home of Professional Open Source
+ Copyright 2006, JBoss Inc., and individual contributors as indicated
+ by the @authors tag. All rights reserved.
+ See the copyright.txt in the distribution for a full listing
+ of individual contributors.
+ This copyrighted material is made available to anyone wishing to use,
+ modify, copy, or redistribute it subject to the terms and conditions
+ of the GNU General Public License, v. 2.0.
+ This program is distributed in the hope that it will be useful, but WITHOUT A
+ WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS FOR A
+ PARTICULAR PURPOSE. See the GNU General Public License for more details.
+ You should have received a copy of the GNU General Public License,
+ v. 2.0 along with this distribution; if not, write to the Free Software
+ Foundation, Inc., 51 Franklin Street, Fifth Floor, Boston,
+ MA 02110-1301, USA.
+
+ (C) 2005-2006,
+ @author JBoss Inc.
+-->
+<page title="JBoss (a Division of Redhat): Trail map: JBossTS Failure Recovery" rootpath="../..">
+ <header>
+ Trail map: JBossTS - Failure Recovery
+ </header>
+ <content>
+ <navigation>
+ <links include="includes/www_arjuna_com_navigation.xml"/>
+ <links include="includes/trailmap_navigation.xml"/>
+ <links title="Navigation">
+ <link ref="index.html">Home</link>
+ </links>
+ <links include="includes/trailmap_additional.xml"/>
+ </navigation>
+ <area title="JBossTS Failure Recovery">
+ <html>
+ <p>The failure recovery subsystem of JBossTS will ensure that results of
+a transaction are applied consistently to all resources affected by the
+transaction, even if any of the application processes or the machine hosting
+them crash or lose network connectivity. In the case of machine (system)
+crash or network failure, the recovery will not take place until the system
+or network are restored, but the original application does not need to
+be restarted recovery responsibility is delegated to the Recovery Manager
+process (see below). Recovery after failure requires that information about
+the transaction and the resources involved survives the failure and is
+accessible afterward: this information is held in the ActionStore, which
+is part of the ObjectStore. If the ObjectStore is destroyed or modified,
+recovery may not be possible.
+<br>Until the recovery procedures are complete, resources affected by a
+transaction that was in progress at the time of the failure may be inaccessible.
+For database resources, this may be reported as tables or rows held by
+"in-doubt transactions". </br>
+ </p>
+ <h4>The Recovery Manager</h4>
+The Recovery Manager is a daemon process responsible for performing crash
+recovery. Only one Recovery Manager runs per node. The Object Store provides
+persistent data storage for transactions to log data. During normal transaction
+processing each transaction will log persistent data needed for the commit
+phase to the Object Store. On successfully committing a transaction this
+data is removed, however if the transaction fails then this data remains
+within the Object Store.
+<br>The Recovery Manager functions by:</br>
+ <ul>
+ <li>
+Periodically scanning the Object Store for transactions that may have failed.
+Failed transactions are indicated by the presence of log data after a period
+of time that the transaction would have normally been expected to finish.</li>
+ <li>
+Checking with the application process which originated the transaction
+whether the transaction is still in progress or not.</li>
+ <li>
+Recovering the transaction by re-activating the transaction and then replaying
+phase two of the commit protocol.</li>
+ </ul>
+To start the Recovery Manager issue the following command:
+
+<pre>
+java com.arjuna.ats.arjuna.recovery.RecoveryManager
+</pre>
+
+If the -test flag is used with the Recovery Manager then it will display a "Ready" message when initialised, i.e.,
+
+<pre>
+java com.arjuna.ats.arjuna.recovery.RecoveryManager -test
+</pre>
+
+On initialization the Recovery Manager first loads in configuration information
+via a properties file. This configuration includes a number of recovery
+activators and recovery modules, which are then dynamically loaded.
+<br>Each recovery activator, which implements the
+<font face="Courier New,Courier">com.arjuna.ats.arjuna.recovery.RecoveryActivator</font>
+interface, is used to instantiate a recovery class related to the underlying
+communication protocol. Indeed, since the version 3.0 of JBossTS, the
+Recovery Manager is not specifically tied to an Object Request Broker or
+ORB, which is to specify a recovery instance able to manage the OTS recovery
+protocol the new interface RecoveryActivator is provided to identify specific
+transaction protocol. For instance, when used with OTS, the RecoveryActivitor
+has the responsibility to create a RecoveryCoordinator object able to respond
+to the replay_completion operation.</br>
+ <br>
+All RecoveryActivator instances inherit the same interface. They are loaded via
+the following recovery extension property:
+</br>
+ <pre>
+<property
+ name="com.arjuna.ats.arjuna.recovery.recoveryActivator_<number>"
+ value="RecoveryClass"/>
+</pre>
+ <p>For instance the RecoveryActivator provided in the distribution of JTS/OTS, which shall not be commented, is as follow : </p>
+ <pre>
+<property
+ name="com.arjuna.ats.arjuna.recovery.recoveryActivator_1"
+ value="com.arjuna.ats.internal.jts.
+ orbspecific.recovery.RecoveryEnablement"/>
+</pre>
+Each recovery module, which implements the <font face="Courier New,Courier">com.arjuna.ats.arjuna.recovery.RecoveryModule</font>
+interface, is used to recover a different type of transaction/resource,
+however each recovery module inherits the same basic behaviour.
+<br>Recovery consists of two separate passes/phases separated by two timeout
+periods. The first pass examines the object store for potentially failed
+transactions; the second pass performs crash recovery on failed transactions.
+The timeout between the first and second pass is known as the backoff period.
+The timeout between the end of the second pass and the start of the first
+pass is the recovery period. The recovery period is larger than the backoff
+period.</br>
+ <br>The Recovery Manager invokes the first pass upon each recovery module,
+applies the backoff period timeout, invokes the second pass upon each recovery
+module and finally applies the recovery period timeout before restarting
+the first pass again.</br>
+ <br>The recovery modules are loaded via the following recovery extension property:</br>
+ <pre>
+com.arjuna.ats.arjuna.recovery.recoveryExtension<number>=<RecoveryClass>
+</pre>
+The default RecoveryExtension settings are:
+
+<pre>
+<property name="com.arjuna.ats.arjuna.recovery.recoveryExtension1"
+ value="com.arjuna.ats.internal.
+ arjuna.recovery.AtomicActionRecoveryModule"/>
+<property name="com.arjuna.ats.arjuna.recovery.recoveryExtension2"
+ value="com.arjuna.ats.internal.
+ txoj.recovery.TORecoveryModule"/>
+<property name="com.arjuna.ats.arjuna.recovery.recoveryExtension3"
+ value="com.arjuna.ats.internal.
+ jts.recovery.transactions.TopLevelTransactionRecoveryModule"/>
+<property name="com.arjuna.ats.arjuna.recovery.recoveryExtension4"
+ value="com.arjuna.ats.internal.
+ jts.recovery.transactions.ServerTransactionRecoveryModule"/>
+</pre>
+ <h4>Configuring the Recovery Manager</h4>
+ <h5>Periodic Recovery</h5>
+The backoff period and recovery period are set using the following properties:
+
+<pre>
+com.arjuna.ats.arjuna.recovery.recoveryBackoffPeriod (default 10 secs)
+com.arjuna.ats.arjuna.recovery.periodicRecovery (default 120 secs)
+</pre>
+ <h5>Expired entry removal</h5>
+The operation of the recovery subsystem will cause some entries to be made
+in the ObjectStore that will not be removed in normal progress. The RecoveryManager
+has a facility for scanning for these and removing items that are very
+old. Scans and removals are performed by implementations of the <font face="Courier New,Courier">com.arjuna.ats.arjuna.recovery.ExpiryScanner</font>.
+Implementations of this interface are loaded by giving the class name as
+the value of a property whose name begins with <font face="Courier New,Courier">ExperyScanner</font>.
+<br>The RecoveryManager calls the scan() method on each loaded ExpiryScanner
+implementation at an interval determined by the property <font face="Courier New,Courier">com.arjuna.ats.arjuna.recovery.expiryScanInterval</font>.
+This value is given in hours default is 12. An EXPIRY_SCAN_INTERVAL value
+of zero will suppress any expiry scanning. If the value as supplied is
+positive, the first scan is performed when RecoveryManager starts; if the
+value is negative, the first scan is delayed until after the first interval
+(using the absolute value)</br>
+ <br>The default ExpiryScanner is:</br>
+ <pre>
+<property
+ name="com.arjuna.ats.arjuna.recovery.
+ expiryScannerTransactionStatusManager"
+ value="com.arjuna.ats.internal.arjuna.recovery.
+ ExpiredTransactionStatusManagerScanner"/>
+ </pre>
+ <p>The following table summarize properties used by the Recovery Manager. These
+ properties are defined by default the properties file named RecoveryManager-properties.xml.
+</p>
+ <table BORDER="" WIDTH="100%">
+ <tr ALIGN="CENTER" BGCOLOR="#66FFFF">
+ <td width="38%">
+ <b>Name</b>
+ </td>
+ <td width="34%">
+ <b>Description</b>
+ </td>
+ <td width="9%">
+ <b>Possible Value</b>
+ </td>
+ <td width="19%">
+ <b>Default Value</b>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ <font size="-7">com.arjuna.ats.arjuna.<br/>
+ recovery.periodicRecoveryPeriod</font>
+ </td>
+ <td>
+ <font size="-7">Interval in seconds between initiating the periodic recovery modules</font>
+ </td>
+ <td>
+ <font size="-7">Value in seconds</font>
+ </td>
+ <td>
+ <font size="-7">120</font>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ <font size="-7">com.arjuna.ats.arjuna.<br/>
+ recovery.recoveryBackoffPeriod</font>
+ </td>
+ <td>
+ <font size="-7">Interval in seconds between first and second pass of periodic recovery</font>
+ </td>
+ <td>
+ <font size="-7">Value in seconds</font>
+ </td>
+ <td>
+ <font size="-7">10</font>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ <font size="-7">com.arjuna.ats.arjuna.<br/>
+ recovery.recoveryExtensionX</font>
+ </td>
+ <td>
+ <font size="-7">Indicates a periodic recovery module to use. X is the occurence number
+ of the recovery module among a set of recovery modules. These modules are
+ invoked in sort-order of names</font>
+ </td>
+ <td>
+ <font size="-6">The class name of the periodic recovery module </font>
+ </td>
+ <td>
+ <font size="-8">JBossTS provides a set classes given in the RecoveryManager-properties.xml file</font>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ <font size="-7">com.arjuna.ats.arjuna.<br/>
+ recovery.recoveryActivator_X</font>
+ </td>
+ <td>
+ <font size="-7">Indicates a recovery activator to use. X is the occurence number of the
+ recovery activator among a set of recovery activators. </font>
+ </td>
+ <td>
+ <font size="-7">The class name of the periodic recovery activator</font>
+ </td>
+ <td>
+ <font size="-7">JBossTS provide one class that manages the recovery protocol specified
+ by the OTS specification </font>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ <font size="-7">com.arjuna.ats.arjuna.<br/>
+ recovery.expiryScannerXXX</font>
+ </td>
+ <td>
+ <font size="-7">Expiry scanners to use (order of invocation is random). Names must begin
+ with "com.arjuna.ats.arjuna.<br/>recovery.expiryScanner"</font>
+ </td>
+ <td>
+ <font size="-7">Class name</font>
+ </td>
+ <td>
+ <font size="-7">JBossTS provides one class given in the RecoveryManager-properties.xml file</font>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ <font size="-7">com.arjuna.ats.arjuna.<br/>
+ recovery.expiryScanInterval</font>
+ </td>
+ <td>
+ <font size="-7">Interval, in hours, between running the expiry scanners. This can be
+ quite long. The absolute value determines the interval - if the value is
+ negative, the scan will NOT be run until after one interval has elapsed.
+ If positive the first scan will be immediately
+ after startup. Zero will prevent any scanning. </font>
+ </td>
+ <td>
+ <font size="-7">Value in hours</font>
+ </td>
+ <td>
+ <font size="-7">12 </font>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ <font size="-7">com.arjuna.ats.arjuna.recovery.<br/>
+ transactionStatusManagerExpiryTime</font>
+ </td>
+ <td>
+ <font size="-7">Age, in hours, for removal of transaction status manager item. This should
+ be longer than any ts-using process will remain running. Zero = Never removed.
+ </font>
+ </td>
+ <td>
+ <font size="-7">Value in Hours</font>
+ </td>
+ <td>
+ <font size="-7">12 </font>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ <font size="-7">com.arjuna.ats.arjuna.recovery<br/>
+ transactionStatusManagerPort</font>
+ </td>
+ <td>
+ <font size="-7">Use this to fix the port on which the TransactionStatusManager listens</font>
+ </td>
+ <td>
+ <font size="-7">Port number (short) </font>
+ </td>
+ <td>
+ <font size="-7">use a free port</font>
+ </td>
+ </tr>
+ </table>
+ </html>
+ </area>
+ </content>
+ <footer/>
+</page>
Modified: labs/jbosstm/trunk/ArjunaJTS/trailmap/docs/includes/trailmap_additional.xml
===================================================================
--- labs/jbosstm/trunk/ArjunaJTS/trailmap/docs/includes/trailmap_additional.xml 2006-09-24 05:52:34 UTC (rev 6395)
+++ labs/jbosstm/trunk/ArjunaJTS/trailmap/docs/includes/trailmap_additional.xml 2006-09-24 07:16:18 UTC (rev 6396)
@@ -1,22 +1,35 @@
<?xml version="1.0"?>
<!--
- JBoss, Home of Professional Open Source
- Copyright 2006, JBoss Inc., and individual contributors as indicated
- by the @authors tag. All rights reserved.
- See the copyright.txt in the distribution for a full listing
- of individual contributors.
- This copyrighted material is made available to anyone wishing to use,
- modify, copy, or redistribute it subject to the terms and conditions
- of the GNU General Public License, v. 2.0.
- This program is distributed in the hope that it will be useful, but WITHOUT A
- WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS FOR A
- PARTICULAR PURPOSE. See the GNU General Public License for more details.
- You should have received a copy of the GNU General Public License,
- v. 2.0 along with this distribution; if not, write to the Free Software
- Foundation, Inc., 51 Franklin Street, Fifth Floor, Boston,
- MA 02110-1301, USA.
-
- (C) 2005-2006,
- @author JBoss Inc.
+ JBoss, Home of Professional Open Source
+ Copyright 2006, JBoss Inc., and individual contributors as indicated
+ by the @authors tag. All rights reserved.
+ See the copyright.txt in the distribution for a full listing
+ of individual contributors.
+ This copyrighted material is made available to anyone wishing to use,
+ modify, copy, or redistribute it subject to the terms and conditions
+ of the GNU General Public License, v. 2.0.
+ This program is distributed in the hope that it will be useful, but WITHOUT A
+ WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS FOR A
+ PARTICULAR PURPOSE. See the GNU General Public License for more details.
+ You should have received a copy of the GNU General Public License,
+ v. 2.0 along with this distribution; if not, write to the Free Software
+ Foundation, Inc., 51 Franklin Street, Fifth Floor, Boston,
+ MA 02110-1301, USA.
+
+ (C) 2005-2006,
+ @author JBoss Inc.
-->
- <links title="Additional Trails"> <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 J2EE</link> <link ref="ArjunaTS_Configuration.html">Configuring ATS</link> <link ref="ArjunaTS_Recovery.html">Configuring the Recovery Manager</link> <link ref="ArjunaTS_ORBPortability.html">ORB Portability</link> <link ref="part6_txoj_introduction.html">Transactional Object For Java</link> </links>
+<links title="Additional Trails">
+ <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 J2EE</link>
+ <link ref="JBossTS_Configuration.html">Configuring ATS</link>
+ <link ref="JBossTS_Recovery.html">
+ Configuring the Recovery Manager
+ </link>
+ <link ref="JBossTS_ORBPortability.html">ORB Portability</link>
+ <link ref="part6_txoj_introduction.html">
+ Transactional Object For Java
+ </link>
+</links>
Modified: labs/jbosstm/trunk/ArjunaJTS/trailmap/docs/index.xml
===================================================================
--- labs/jbosstm/trunk/ArjunaJTS/trailmap/docs/index.xml 2006-09-24 05:52:34 UTC (rev 6395)
+++ labs/jbosstm/trunk/ArjunaJTS/trailmap/docs/index.xml 2006-09-24 07:16:18 UTC (rev 6396)
@@ -34,10 +34,10 @@
</navigation>
<area title="Introduction">
<html>
- <p>Arjuna Transaction Service 4.0 (ATS 4.0) assures complete, accurate business
+ <p>JBoss Transaction Service (JBossTS) assures complete, accurate business
transactions for any Java based applications, including those written for the
J2EE and EJB frameworks.</p>
- <p>ArjunaTS is a 100% Java implementation of a
+ <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 J2EE 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
@@ -46,7 +46,7 @@
Java objects to participate in transactions, one of the key features of ATS
is it's 100% Java implementation. This allows ATS to support fully distributed
transactions that can be coordinated by distributed parties.
-<p>ArjunaTS runs can be run both as an embedded distributed service of an application
+<p>JBossTS runs can be run both as an embedded distributed service of an application
server (e.g., HPAS. JBoss), affording the user all the added benefits of the
application server environment such as real-time load balancing, unlimited linear
scalability and unmatched fault tolerance that allows you to deliver an always-on
@@ -108,9 +108,9 @@
It is structured as follows:</p>
<ul>
<li>
- <a class="linkscoloured" href="part1.html">1. Installation Content</a>: This trail describes the content installed by the ArjunaTS distribution </li>
+ <a class="linkscoloured" href="part1.html">1. Installation Content</a>: This trail describes the content installed by the JBossTS distribution </li>
<li>
- <a class="linkscoloured" href="part4.html">2. The Sample Application</a>: This trail describes via a set of examples how ArjunaTS is used to build transactional applications</li>
+ <a class="linkscoloured" href="part4.html">2. The Sample Application</a>: This trail describes via a set of examples how JBossTS is used to build transactional applications</li>
<li>
<a class="linkscoloured" href="part5.html">3. Deploying and testing the Sample Application</a>: This trail describes how to deploy and to test the sample application</li>
<li>
Modified: labs/jbosstm/trunk/ArjunaJTS/trailmap/docs/next.xml
===================================================================
--- labs/jbosstm/trunk/ArjunaJTS/trailmap/docs/next.xml 2006-09-24 05:52:34 UTC (rev 6395)
+++ labs/jbosstm/trunk/ArjunaJTS/trailmap/docs/next.xml 2006-09-24 07:16:18 UTC (rev 6396)
@@ -33,10 +33,10 @@
</navigation>
<area title="Where next?">
<html>
- <p> For further information, please consult the documentation sets for ArjunaTS </p>
+ <p> For further information, please consult the documentation sets for JBossTS </p>
<ul>
<li>
- <a class="linkscoloured" href="../../docs/user_guide/QuickStartGuide.pdf" target="_blank">ArjunaTS Quick Start Guide (pdf)</a> Additional documentation for the ArjunaTS product can be found in the <a class="linkscoloured" href="../../index.html" target="_blank">ArjunaTS documentation</a> directory.</li>
+ <a class="linkscoloured" href="../../docs/user_guide/QuickStartGuide.pdf" target="_blank">JBossTS Quick Start Guide (pdf)</a> Additional documentation for the JBossTS product can be found in the <a class="linkscoloured" href="../../index.html" target="_blank">JBossTS documentation</a> directory.</li>
</ul>
<p> Updates to the Arjuna products set, as well as additional sample material, are periodically made available via the Arjuna Technologies web site at <a class="linkscoloured" href="http://www.arjuna.com/" target="_blank">http://www.arjuna.com/</a> Please drop by from time to time to ensure you have the most comprehensive material available. If you experience difficulties using Arjuna products standalone or in conjunction with the JBoss platform, please contact <a class="linkscoloured" href="mailto:support at arjuna.com">support at arjuna.com</a>
</p>
Modified: labs/jbosstm/trunk/ArjunaJTS/trailmap/docs/part1.xml
===================================================================
--- labs/jbosstm/trunk/ArjunaJTS/trailmap/docs/part1.xml 2006-09-24 05:52:34 UTC (rev 6395)
+++ labs/jbosstm/trunk/ArjunaJTS/trailmap/docs/part1.xml 2006-09-24 07:16:18 UTC (rev 6396)
@@ -36,24 +36,24 @@
<area title="Installation Content">
<html>
<h4>Verifying Installation</h4>
-By default, ArjunaTS is installed in the directory <font face="Courier New,Courier">/opt/arjuna/ats-4.0</font>
+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 ArjunaTS
-installation. When installed, the ArjunaTS should have the following structure.
+on Windows, except if a different location has been specified during JBossTS
+installation. When installed, the JBossTS should have the following structure.
<ul>
<li>
<font face="Courier New,Courier">/bin</font>: this directory contains commands
to run the OTS transaction manager server (if required) and the Recovery Manager,
- and scripts to configure environment variables needed to execute ArjunaTS.</li>
+ and scripts to configure environment variables needed to execute JBossTS.</li>
<li>
<font face="Courier New,Courier">/docs</font>: this directory contains
documentation on the way to installing, administering and programming ArjunaCore,
- ArjunaTA and ArjunaTS.</li>
+ ArjunaTA and JBossTS.</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 Arjuna Transaction Service.</li>
+ properties files that can be used to configure the behaviour of the JBoss Transaction Service.</li>
<li>
<font face="Courier New,Courier">/htdocs</font>: this directory describes
- all APIs defined by ArjunaTS
+ all APIs defined by JBossTS
</li>
<li>
<font face="Courier New,Courier">/idl</font>: this directory contains the
@@ -65,7 +65,7 @@
</li>
<li>
<font face="Courier New,Courier">/lib</font>: this directory contains the
- jar files that contains packages defined by the ArjunaTS. These jar files
+ jar files that contains packages defined by the JBossTS. These jar files
shall be added in the CLASSPATH
</li>
<li>
@@ -79,27 +79,27 @@
</ul>
<h4>
<a name="TestInstall"/>Testing your installation</h4>
- <p>To ensure that your ArjunaTS installation is fully operational, we will run the simple demo.</p>
+ <p>To ensure that your JBossTS installation is fully operational, we will run the simple demo.</p>
<p>Please follow these steps before running the transactional applications</p>
<ul>
<li>Ensure you have the Ant build system installed. Ant is a Java build tool,
similar to make. It is available for free from http://ant.apache.org/ The
sample application requires version 1.5.1 or later. </li>
<li>The PATH and CLASSPATH environment variables need to be set appropriately
- to use Arjuna Transaction Service. To make this easier, we provide a shell
+ to use JBoss Transaction Service. To make this easier, we provide a shell
script <font face="Courier New, Courier, mono">setup_env.sh</font> (and for
Windows a batch file <font face="Courier New, Courier, mono">setup_env.bat</font>)
- in the directory <font face="Courier New, Courier, mono"><arjunats_install_root>/bin/</font>
+ in the directory <font face="Courier New, Courier, mono"><jbossts_install_root>/bin/</font>
</li>
<li>From a command prompt, cd to the directory containing the build.xml file
- (<font face="Courier New, Courier, mono"><arjunats_install_root>/trail_map</font>)
- and type 'ant'. This will compile a set of sources files located under <font face="Courier New, Courier, mono"><arjunats_install_root>/trail_map/src</font>
- then create an application .jar file named <em>arjunats-demo.jar</em>. under
- the directory <font face="Courier New, Courier, mono"><arjunats_install_root>/trail_map/lib</font>
+ (<font face="Courier New, Courier, mono"><jbossts_install_root>/trail_map</font>)
+ and type 'ant'. This will compile a set of sources files located under <font face="Courier New, Courier, mono"><jbossts_install_root>/trail_map/src</font>
+ then create an application .jar file named <em>jbossts-demo.jar</em>. under
+ 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/>
- <b>Ensure that ArjunaTS jar files appear before jacorb jar files. </b></li>
+ <b>Ensure that JBossTS jar files appear before jacorb jar files. </b></li>
</ul>
<ul>
<li> Start the server. <a class="linkscoloured" href="../src/com/arjuna/demo/simple/HelloServer.java">(HelloServer.java)</a> (<i>Note: The source code for the trailmap is fully documented and can often contain very useful tips and information that may not be reflected elsewhere in the trailmap</i>)</li>
@@ -130,11 +130,11 @@
Hello - called within a scope of a transaction</pre>
<h4>Setting properties</h4>
-The Arjuna Transaction Service has been designed to be highly configurable at runtime through the use of various
+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 ATS distribution.
- <p>More details on the way to configure the behavior of ArjunaTS can be found <a class="linkscoloured" href="ArjunaTS_Configuration.html">here</a>.
+ <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>
<h4>Specifying the ORB to use</h4>
@@ -142,10 +142,10 @@
If using such a JDK in conjunction with another ORB it is necessary to tell
the JVM which ORB to use. This happens by specifying the org.omg.CORBA.ORBClass
<br/>
- and org.omg.CORBA.ORBSingletonClass properties. In earlier versions of the ArjunaTS
+ and org.omg.CORBA.ORBSingletonClass properties. In earlier versions of the JBossTS
it was necessary to specify these properties explicitly, either on the command
line of in the properties file. However, it is no longer a requirement to do
- this, as the <a class="linkscoloured" href="ArjunaTS_ORBPortability.html">ORB Portability</a> classes
+ this, as the <a class="linkscoloured" href="JBossTS_ORBPortability.html">ORB Portability</a> classes
will ensure that these properties are automatically set when required. Of course
it is still possible to specify these values explicitly (and necessary if not
using the ORB initialization methods)</p>
Modified: labs/jbosstm/trunk/ArjunaJTS/trailmap/docs/part2.xml
===================================================================
--- labs/jbosstm/trunk/ArjunaJTS/trailmap/docs/part2.xml 2006-09-24 05:52:34 UTC (rev 6395)
+++ labs/jbosstm/trunk/ArjunaJTS/trailmap/docs/part2.xml 2006-09-24 07:16:18 UTC (rev 6396)
@@ -1,22 +1,627 @@
<?xml version="1.0"?>
<!--
- JBoss, Home of Professional Open Source
- Copyright 2006, JBoss Inc., and individual contributors as indicated
- by the @authors tag. All rights reserved.
- See the copyright.txt in the distribution for a full listing
- of individual contributors.
- This copyrighted material is made available to anyone wishing to use,
- modify, copy, or redistribute it subject to the terms and conditions
- of the GNU General Public License, v. 2.0.
- This program is distributed in the hope that it will be useful, but WITHOUT A
- WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS FOR A
- PARTICULAR PURPOSE. See the GNU General Public License for more details.
- You should have received a copy of the GNU General Public License,
- v. 2.0 along with this distribution; if not, write to the Free Software
- Foundation, Inc., 51 Franklin Street, Fifth Floor, Boston,
- MA 02110-1301, USA.
-
- (C) 2005-2006,
- @author JBoss Inc.
+ JBoss, Home of Professional Open Source
+ Copyright 2006, JBoss Inc., and individual contributors as indicated
+ by the @authors tag. All rights reserved.
+ See the copyright.txt in the distribution for a full listing
+ of individual contributors.
+ This copyrighted material is made available to anyone wishing to use,
+ modify, copy, or redistribute it subject to the terms and conditions
+ of the GNU General Public License, v. 2.0.
+ This program is distributed in the hope that it will be useful, but WITHOUT A
+ WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS FOR A
+ PARTICULAR PURPOSE. See the GNU General Public License for more details.
+ You should have received a copy of the GNU General Public License,
+ v. 2.0 along with this distribution; if not, write to the Free Software
+ Foundation, Inc., 51 Franklin Street, Fifth Floor, Boston,
+ MA 02110-1301, USA.
+
+ (C) 2005-2006,
+ @author JBoss Inc.
-->
-<page title="Arjuna Technologies Limited: Trail map: Overview of the Distributed Transaction Processing" rootpath="../.."> <header> Trail map: Overview of the Distributed Transaction Processing </header> <content> <navigation> <links include="includes/www_arjuna_com_navigation.xml"/> <links include="includes/trailmap_navigation.xml"/> <links title="Navigation"> <link ref="index.html">Home</link> <link ref="part1.html">Previous</link> <link ref="part3.html">Next</link> </links> </navigation> <area title="Overview of the Distributed Transaction Processing"> <html> <h4>What is a Transaction</h4> <p>Transaction management is one of the most crucial requirements for enterprise application development. Most of the large enterprise applications in the domains of finance, banking and electronic commerce rely on transaction processing for delivering their business functionality. </p> <p>Enterprise applications often !
require concurrent access to distributed data shared amongst multiple components, to perform operations on data. Such applications should maintain integrity of data (as defined by the business rules of the application) under the following circumstances: </p> <ul> <li>distributed access to a single resource of data, and </li> <li>access to distributed resources from a single application component. </li> </ul> <p>In such cases, it may be required that a group of operations on (distributed) resources be treated as one unit of work. In a unit of work, all the participating operations should either succeed or fail and recover together. This problem is more complicated when </p> <ul> <li>a unit of work is implemented across a group of distributed components operating on data from multiple resources, and/or </li> <li>the participating operations are executed sequentially or in parallel threads requiring coordination and/or synchro!
nization. </li> </ul> <p>In either case, it is required that s
uccess or failure of a unit of work be maintained by the application. In case of a failure, all the resources should bring back the state of the data to the previous state (<i>i.e.,</i> the state prior to the commencement of the unit of work). </p> <p> From the programmer's perspective a transaction is a scoping mechanism for a collection of actions which must complete as a unit. It provides a simplified model for exception handling since only two outcomes are possible: </p> <ul> <li> success - meaning that all actions involved within a transaction are completed </li> <li> failure - no actions complete </li> </ul> <img src="includes/trans_succes_failure.GIF"/> <h5>Example</h5> <br> To illustrate the reliability expected by the application let’s consider the funds transfer example which is familiar to all of us. </br> The Money transfer involves two operations: Deposit and Withdrawal <br> !
The complexity of implementation doesn't matter; money moves from one place to another. For instance, involved accounts may be either located in a same relational table within a database or located on different databases. </br> <br> A Simple transfer consists on moving money from savings to checking while a Complex transfer can be performed at the end- of- day according to a reconciliation between international banks </br> <img border="0" src="includes/example_transfer.GIF"/> <a name="Introduction"> <a name="What is a Transaction"/> <p>The concept of a transaction, and a transaction manager (or a transaction processing service) simplifies construction of such enterprise level distributed applications while maintaining integrity of data in a unit of work. </p> </a> <p>A transaction is a unit of work that has the following properties: </p> <ul> <li> <strong>Atomicity</strong> – either th!
e whole transaction completes or nothing completes - partial comp
letion is not permitted. </li> <li> <strong>Consistency</strong> – a transaction transforms the system from one consistent state to another. In other words, On completion of a successful transaction, the data should be in a consistent state. For example, in the case of relational databases, a consistent transaction should preserve all the integrity constraints defined on the data. </li> <li> <b>Isolation:</b> Each transaction should appear to execute independently of other transactions that may be executing concurrently in the same environment. The effect of executing a set of transactions serially should be the same as that of running them concurrently. This requires two things: <ul> <li>During the course of a transaction, intermediate (possibly inconsistent) state of the data should not be exposed to all other transactions. </li> <li>Two concurrent transactions should not be abl!
e to operate on the same data. Database management systems usually implement this feature using locking. </li> </ul> </li> <li> <b>Durability:</b> The effects of a completed transaction should always be persistent. </li> </ul> <p>These properties, called as <b>ACID</b> properties, guarantee that a transaction is never incomplete, the data is never inconsistent, concurrent transactions are independent, and the effects of a transaction are persistent. </p> <h4>Transactional Concepts</h4> <h5>Transaction Components</h5> <p>A collection of actions is said to be transactional if they possess the ACID properties. These properties are assumed to be ensured, in the presence of failures; if actions involved within the transaction are performed by a Transactional System. A transaction system includes a set of components where each of them has a particular role. Main components are described below. </p> <div s!
tyle="mso-line-spacing:"100 30 0";mso-char-wrap:1;mso-kinsok
u-overflow:1"> <img border="0" src="includes/transaction_components.GIF"/> <h5> <span style="font-family: Times New Roman" lang="en-gb">Application Programs</span> </h5> <p>Application Programs are clients for the transactional resources. These are the programs with which the application developer implements business transactions. With the help of the transaction manager, these components create global transactions and operate on the transactional resources with in the scope of these transactions. These components are not responsible for implementing mechanisms for preserving ACID properties of transactions. However, as part of the application logic, these components generally make a decision whether to commit or rollback transactions.</p> <p>Application responsibilities could be summarized as follow:</p> <ul> <li>Create and demarcate transactions </li> <li>Operate on data!
via resource managers</li> </ul> <h5> <span style="font-family: Times New Roman" lang="en-gb">Resource Managers</span> </h5> <p>A resource manager is in general a component that manages persistent and stable data storage system, and participates in the two phase commit and recovery protocols with the transaction manager. </p> <p>A resource manager is typically a driver that provides two sets of interfaces: one set for the application components to get connections and operating, and the other set for participating in two phase commit and recovery protocols coordinated by a transaction manager. This component may also, directly or indirectly, register resources with the transaction manager so that the transaction manager can keep track of all the resources participating in a transaction. This process is called as resource enlistment. </p> <p>Resource Manager responsibili!
ties could be summarized as follow</p> <ul> <li>Enlist reso
urces with the transaction manager </li> <li>Participate in two-phase commit and recovery protocol </li> </ul> <h5> <span lang="en-gb"> <font face="Times New Roman">Transaction Manager</font> </span> </h5> <p>The transaction manager is the core component of a transaction processing environment. Its main responsibilities are to create transactions when requested by application components, allow resource enlistment and delistment, and to manage the two-phase commit or recovery protocol with the resource managers. </p> <p>A typical transactional application begins a transaction by issuing a request to a transaction manager to initiate a transaction. In response, the transaction manager starts a transaction and associates it with the calling thread. The transaction manager also establishes a transaction context. All application components and/or threads participating in the !
transaction share the transaction context. The thread that initially issued the request for beginning the transaction, or, if the transaction manager allows, any other thread may eventually terminate the transaction by issuing a commit or rollback request. </p> <p>Before a transaction is terminated, any number of components and/or threads may perform transactional operations on any number of transactional resources known to the transaction manager. If allowed by the transaction manager, a transaction may be suspended or resumed before finally completing the transaction. </p> <p>Once the application issues the commit request, the transaction manager prepares all the resources for a commit operation, and based on whether all resources are ready for a commit or not, issues a commit or rollback request to all the resources.</p> <p>Resource Manager responsibilities could be summarized as !
follow:</p> <ul> <li>Establish and maintain transaction con
text </li> <li>Maintain association between a transaction and the participating resources. </li> <li>Initiate and conduct two-phase commit and recovery protocol with the resource managers. </li> <li>Make synchronization calls to the application components before beginning and after end of the two-phase commit and recovery process </li> </ul> </div> <h5>Local vs. Distributed Transaction</h5> <p> A transaction that involves only one transactional resource, such a database, is considered as <i>local transaction</i>, while a transaction that involves more than one transactional resource that need to be coordinated to reach a consistent state is considered as a <i>distributed transaction.</i> </p> <p>A transaction can be specified by what is known as transaction demarcation. Transaction demarcation enables work done by distributed components to be bound by a global transaction. It i!
s a way of marking groups of operations to constitute a transaction. </p> <p>The most common approach to demarcation is to mark the thread executing the operations for transaction processing. This is called as programmatic demarcation. The transaction so established can be suspended by unmarking the thread, and be resumed later by explicitly propagating the transaction context from the point of suspension to the point of resumption. </p> <p>The transaction demarcation ends after a commit or a rollback request to the transaction manager. The commit request directs all the participating resources managers to record the effects of the operations of the transaction permanently. The rollback request makes the resource managers undo the effects of all operations on the transaction. </p> <h5>Transaction Context and Propagation </h5> <p>Since multiple application components and resources participate in a transaction, it is necessary for!
the transaction manager to establish and maintain the state of the
transaction as it occurs. This is usually done in the form of transaction context. </p> <p>Transaction context is an association between the transactional operations on the resources, and the components invoking the operations. During the course of a transaction, all the threads participating in the transaction share the transaction context. Thus the transaction context logically envelops all the operations performed on transactional resources during a transaction. The transaction context is usually maintained transparently by the underlying transaction manager. </p> <h5>Resource Enlistment</h5> <p>Resource enlistment is the process by which resource managers inform the transaction manager of their participation in a transaction. This process enables the transaction manager to keep track of all the resources participating in a transaction. The transaction manager uses this information to coordinate transactional work performed by!
the resource managers and to drive two-phase and recovery protocol. At the end of a transaction (after a commit or rollback) the transaction manager delists the resources. </p> <h5> <a name="2pc"/>Two-Phase Commit</h5> <p>This protocol between the transaction manager and all the resources enlisted for a transaction ensures that either all the resource managers commit the transaction or they all abort. In this protocol, when the application requests for committing the transaction, the transaction manager issues a prepare request to all the resource managers involved. Each of these resources may in turn send a reply indicating whether it is ready for commit or not. Only The transaction manager issue a commit request to all the resource managers, only when all the resource managers are ready for a commit. Otherwise, the transaction manager issues a rollback request and the transaction will be rolled back. </p> <h5> <a nam!
e="RecoveryLog"/>Recovery and Logging</h5> <div> Basically, the R
ecovery is the mechanism which preserves the transaction atomicity in presence of failures. The basic technique for implementing transactions in presence of failures is based on the use of logs. That is, a transaction system has to record enough information to ensure that it can be able to return to a previous state in case of failure or to ensure that changes committed by a transaction are properly stored. <p> In addition to be able to store appropriate information, all participants within a distributed transaction must log similar information which allow them to take a same decision either to set data in their final state or in their initial state. </p> <p> Two techniques are in general used to ensure transaction's atomicity. A first technique focuses on manipulated data, such the Do/Undo/Redo protocol (considered as a recovery mechanism in a centralized system), which allow a participant to set its data in their final values or!
to retrieve them in their initial values. A second technique relies on a distributed protocol named the two phases commit, ensuring that all participants involved within a distributed transaction set their data either in their final values or in their initial values. In other words all participants must commit or all must rollback. </p> <img border="0" src="includes/recovery_logs.GIF"/> <p/> <p> In addition to failures we refer as centralized such system crashes, communication failures due for instance to <span style="mso-spacerun:yes"/>network outages or message loss have to be considered during the recovery process of a distributed transaction. </p> <p> In order to provide an efficient and optimized mechanism to deal with failure, modern transactional systems typically adopt a “presume abort” strategy, which simplifies the transaction management. !
</p> <p> The presumed abort strategy can be st
ated as «when in doubt, abort». With this strategy, when the recovery mechanism has no information about the transaction, it presumes that the transaction has been aborted. </p> A particularity of the presumed-abort assumption allows a coordinator to not log anything before the commit decision and the participants do not to log anything before they prepare. Then, any failure which occurs before the 2pc starts lead to abort the transaction. Furthermore, from a coordinator point of view any communication failure detected by a timeout or exception raised on sending prepare is considered as a negative vote which leads to abort the transaction. So, within a distributed transaction a coordinator or a participant may fail in two ways: either it crashes or it times out for a message it was expecting. When a coordina!
tor or a participant crashes and then restarts, it uses information on stable storage to determine the way to perform the recovery. As we will see it the presumed-abort strategy enable an optimized behavior for the recovery. </div> <h5>Heuristic Decision</h5> In extremely rare cases, a resource manager may choose not to wait for the outcome from the transaction manager. This might occur if the communications path was lost and was not likely to be restored for a very long time. Typically this happens as a result of human intervention and not as an arbitrary action of a resource manager. In order to release locks and make this transactions data available to new transactions, the resource manager makes a <b>heuristic decision</b>, i.e. it guesses the proper transaction outcome. When it does so, it must remembe!
r its guess until contact with the transaction manager is u
ltimately re-established. <h4>Standards</h4> Saying that a distributed transaction can involve several distributed participants, means that these participant must be integrated within a global transaction manager which has the responsibility to ensure that all participants take a common decision to commit or rollback the distributed transaction. The key of such integration is the existence of a common transactional interface which is understood by all participants, transaction manager and resource managers such databases. <p> The importance of common interfaces between participants, as well as the complexity of their implementation, becomes obvious in an open systems environment. For this aim various distributed transaction processing standards have been developed by international standards organizations. Among these organizations, We list three of them which are mainly !
considered in the Arjuna Transaction Service product: </p> <ul> <li> The <a class="linkscoloured" href="xopen_overview.html">X/Open model </a> and its successful XA interface </li> <li> The OMG with its CORBA infrastructure and the <a class="linkscoloured" href="ots_overview.html">Object Transaction Service</a> and finally </li> <li> The Java Community Process leaded by Sun with its <a class="linkscoloured" href="jta_overview.html"> JTA/JTS specification</a> </li> </ul> Basically these standards have proposed logical models, which divide transaction processing into several functions: <ul> <li> those assigned to the application which ties resources together in application- specific operations </li> <li> those assigned to the Resource manager which access physically to data stores </li> <li> functions perf!
ormed by the Transaction Manager which manages transactions, and fina
lly </li> <li> Communication Resource Managers which allow to exchange information with other transactional domains. </li> </ul> <img border="0" src="includes/standards.GIF"/> </html> </area> </content> <footer/> </page>
+<page
+ title="JBoss (a Division of Redhat): Trail map: Overview of the Distributed Transaction Processing"
+ rootpath="../..">
+ <header>
+ Trail map: Overview of the Distributed Transaction Processing
+ </header>
+ <content>
+ <navigation>
+ <links include="includes/www_arjuna_com_navigation.xml" />
+ <links include="includes/trailmap_navigation.xml" />
+ <links title="Navigation">
+ <link ref="index.html">Home</link>
+ <link ref="part1.html">Previous</link>
+ <link ref="part3.html">Next</link>
+ </links>
+ </navigation>
+ <area
+ title="Overview of the Distributed Transaction Processing">
+ <html>
+ <h4>What is a Transaction</h4>
+ <p>
+ Transaction management is one of the most crucial
+ requirements for enterprise application development.
+ Most of the large enterprise applications in the
+ domains of finance, banking and electronic commerce
+ rely on transaction processing for delivering their
+ business functionality.
+ </p>
+ <p>
+ Enterprise applications often require concurrent
+ access to distributed data shared amongst multiple
+ components, to perform operations on data. Such
+ applications should maintain integrity of data (as
+ defined by the business rules of the application)
+ under the following circumstances:
+ </p>
+ <ul>
+ <li>
+ distributed access to a single resource of data,
+ and
+ </li>
+ <li>
+ access to distributed resources from a single
+ application component.
+ </li>
+ </ul>
+ <p>
+ In such cases, it may be required that a group of
+ operations on (distributed) resources be treated as
+ one unit of work. In a unit of work, all the
+ participating operations should either succeed or
+ fail and recover together. This problem is more
+ complicated when
+ </p>
+ <ul>
+ <li>
+ a unit of work is implemented across a group of
+ distributed components operating on data from
+ multiple resources, and/or
+ </li>
+ <li>
+ the participating operations are executed
+ sequentially or in parallel threads requiring
+ coordination and/or synchronization.
+ </li>
+ </ul>
+ <p>
+ In either case, it is required that success or
+ failure of a unit of work be maintained by the
+ application. In case of a failure, all the resources
+ should bring back the state of the data to the
+ previous state (
+ <i>i.e.,</i>
+ the state prior to the commencement of the unit of
+ work).
+ </p>
+ <p>
+ From the programmer's perspective a transaction is a
+ scoping mechanism for a collection of actions which
+ must complete as a unit. It provides a simplified
+ model for exception handling since only two outcomes
+ are possible:
+ </p>
+ <ul>
+ <li>
+ success - meaning that all actions involved
+ within a transaction are completed
+ </li>
+ <li>failure - no actions complete</li>
+ </ul>
+ <img src="includes/trans_succes_failure.GIF" />
+ <h5>Example</h5>
+ <br>
+ To illustrate the reliability expected by the
+ application let’s consider the funds transfer
+ example which is familiar to all of us.
+ </br>
+ The Money transfer involves two operations: Deposit and
+ Withdrawal
+ <br>
+ The complexity of implementation doesn't matter;
+ money moves from one place to another. For instance,
+ involved accounts may be either located in a same
+ relational table within a database or located on
+ different databases.
+ </br>
+ <br>
+ A Simple transfer consists on moving money from
+ savings to checking while a Complex transfer can be
+ performed at the end- of- day according to a
+ reconciliation between international banks
+ </br>
+ <img border="0" src="includes/example_transfer.GIF" />
+ <a name="Introduction">
+ <a name="What is a Transaction" />
+ <p>
+ The concept of a transaction, and a transaction
+ manager (or a transaction processing service)
+ simplifies construction of such enterprise level
+ distributed applications while maintaining
+ integrity of data in a unit of work.
+ </p>
+ </a>
+ <p>
+ A transaction is a unit of work that has the
+ following properties:
+ </p>
+ <ul>
+ <li>
+ <strong>Atomicity</strong>
+ – either the whole transaction completes or
+ nothing completes - partial completion is not
+ permitted.
+ </li>
+ <li>
+ <strong>Consistency</strong>
+ – a transaction transforms the system from one
+ consistent state to another. In other words, On
+ completion of a successful transaction, the data
+ should be in a consistent state. For example, in
+ the case of relational databases, a consistent
+ transaction should preserve all the integrity
+ constraints defined on the data.
+ </li>
+ <li>
+ <b>Isolation:</b>
+ Each transaction should appear to execute
+ independently of other transactions that may be
+ executing concurrently in the same environment.
+ The effect of executing a set of transactions
+ serially should be the same as that of running
+ them concurrently. This requires two things:
+ <ul>
+ <li>
+ During the course of a transaction,
+ intermediate (possibly inconsistent)
+ state of the data should not be exposed
+ to all other transactions.
+ </li>
+ <li>
+ Two concurrent transactions should not
+ be able to operate on the same data.
+ Database management systems usually
+ implement this feature using locking.
+ </li>
+ </ul>
+ </li>
+ <li>
+ <b>Durability:</b>
+ The effects of a completed transaction should
+ always be persistent.
+ </li>
+ </ul>
+ <p>
+ These properties, called as
+ <b>ACID</b>
+ properties, guarantee that a transaction is never
+ incomplete, the data is never inconsistent,
+ concurrent transactions are independent, and the
+ effects of a transaction are persistent.
+ </p>
+ <h4>Transactional Concepts</h4>
+ <h5>Transaction Components</h5>
+ <p>
+ A collection of actions is said to be transactional
+ if they possess the ACID properties. These
+ properties are assumed to be ensured, in the
+ presence of failures; if actions involved within the
+ transaction are performed by a Transactional System.
+ A transaction system includes a set of components
+ where each of them has a particular role. Main
+ components are described below.
+ </p>
+ <div
+ style="mso-line-spacing:"100 30 0";mso-char-wrap:1;mso-kinsoku-overflow:1">
+ <img border="0"
+ src="includes/transaction_components.GIF" />
+ <h5>
+ <span style="font-family: Times New Roman"
+ lang="en-gb">
+ Application Programs
+ </span>
+ </h5>
+ <p>
+ Application Programs are clients for the
+ transactional resources. These are the programs
+ with which the application developer implements
+ business transactions. With the help of the
+ transaction manager, these components create
+ global transactions and operate on the
+ transactional resources with in the scope of
+ these transactions. These components are not
+ responsible for implementing mechanisms for
+ preserving ACID properties of transactions.
+ However, as part of the application logic, these
+ components generally make a decision whether to
+ commit or rollback transactions.
+ </p>
+ <p>
+ Application responsibilities could be summarized
+ as follow:
+ </p>
+ <ul>
+ <li>Create and demarcate transactions</li>
+ <li>Operate on data via resource managers</li>
+ </ul>
+ <h5>
+ <span style="font-family: Times New Roman"
+ lang="en-gb">
+ Resource Managers
+ </span>
+ </h5>
+ <p>
+ A resource manager is in general a component
+ that manages persistent and stable data storage
+ system, and participates in the two phase commit
+ and recovery protocols with the transaction
+ manager.
+ </p>
+ <p>
+ A resource manager is typically a driver that
+ provides two sets of interfaces: one set for the
+ application components to get connections and
+ operating, and the other set for participating
+ in two phase commit and recovery protocols
+ coordinated by a transaction manager. This
+ component may also, directly or indirectly,
+ register resources with the transaction manager
+ so that the transaction manager can keep track
+ of all the resources participating in a
+ transaction. This process is called as resource
+ enlistment.
+ </p>
+ <p>
+ Resource Manager responsibilities could be
+ summarized as follow
+ </p>
+ <ul>
+ <li>
+ Enlist resources with the transaction
+ manager
+ </li>
+ <li>
+ Participate in two-phase commit and recovery
+ protocol
+ </li>
+ </ul>
+ <h5>
+ <span lang="en-gb">
+ <font face="Times New Roman">
+ Transaction Manager
+ </font>
+ </span>
+ </h5>
+ <p>
+ The transaction manager is the core component of
+ a transaction processing environment. Its main
+ responsibilities are to create transactions when
+ requested by application components, allow
+ resource enlistment and delistment, and to
+ manage the two-phase commit or recovery protocol
+ with the resource managers.
+ </p>
+ <p>
+ A typical transactional application begins a
+ transaction by issuing a request to a
+ transaction manager to initiate a transaction.
+ In response, the transaction manager starts a
+ transaction and associates it with the calling
+ thread. The transaction manager also establishes
+ a transaction context. All application
+ components and/or threads participating in the
+ transaction share the transaction context. The
+ thread that initially issued the request for
+ beginning the transaction, or, if the
+ transaction manager allows, any other thread may
+ eventually terminate the transaction by issuing
+ a commit or rollback request.
+ </p>
+ <p>
+ Before a transaction is terminated, any number
+ of components and/or threads may perform
+ transactional operations on any number of
+ transactional resources known to the transaction
+ manager. If allowed by the transaction manager,
+ a transaction may be suspended or resumed before
+ finally completing the transaction.
+ </p>
+ <p>
+ Once the application issues the commit request,
+ the transaction manager prepares all the
+ resources for a commit operation, and based on
+ whether all resources are ready for a commit or
+ not, issues a commit or rollback request to all
+ the resources.
+ </p>
+ <p>
+ Resource Manager responsibilities could be
+ summarized as follow:
+ </p>
+ <ul>
+ <li>
+ Establish and maintain transaction context
+ </li>
+ <li>
+ Maintain association between a transaction
+ and the participating resources.
+ </li>
+ <li>
+ Initiate and conduct two-phase commit and
+ recovery protocol with the resource
+ managers.
+ </li>
+ <li>
+ Make synchronization calls to the
+ application components before beginning and
+ after end of the two-phase commit and
+ recovery process
+ </li>
+ </ul>
+ </div>
+ <h5>Local vs. Distributed Transaction</h5>
+ <p>
+ A transaction that involves only one transactional
+ resource, such a database, is considered as
+ <i>local transaction</i>
+ , while a transaction that involves more than one
+ transactional resource that need to be coordinated
+ to reach a consistent state is considered as a
+ <i>distributed transaction.</i>
+ </p>
+ <p>
+ A transaction can be specified by what is known as
+ transaction demarcation. Transaction demarcation
+ enables work done by distributed components to be
+ bound by a global transaction. It is a way of
+ marking groups of operations to constitute a
+ transaction.
+ </p>
+ <p>
+ The most common approach to demarcation is to mark
+ the thread executing the operations for transaction
+ processing. This is called as programmatic
+ demarcation. The transaction so established can be
+ suspended by unmarking the thread, and be resumed
+ later by explicitly propagating the transaction
+ context from the point of suspension to the point of
+ resumption.
+ </p>
+ <p>
+ The transaction demarcation ends after a commit or a
+ rollback request to the transaction manager. The
+ commit request directs all the participating
+ resources managers to record the effects of the
+ operations of the transaction permanently. The
+ rollback request makes the resource managers undo
+ the effects of all operations on the transaction.
+ </p>
+ <h5>Transaction Context and Propagation</h5>
+ <p>
+ Since multiple application components and resources
+ participate in a transaction, it is necessary for
+ the transaction manager to establish and maintain
+ the state of the transaction as it occurs. This is
+ usually done in the form of transaction context.
+ </p>
+ <p>
+ Transaction context is an association between the
+ transactional operations on the resources, and the
+ components invoking the operations. During the
+ course of a transaction, all the threads
+ participating in the transaction share the
+ transaction context. Thus the transaction context
+ logically envelops all the operations performed on
+ transactional resources during a transaction. The
+ transaction context is usually maintained
+ transparently by the underlying transaction manager.
+ </p>
+ <h5>Resource Enlistment</h5>
+ <p>
+ Resource enlistment is the process by which resource
+ managers inform the transaction manager of their
+ participation in a transaction. This process enables
+ the transaction manager to keep track of all the
+ resources participating in a transaction. The
+ transaction manager uses this information to
+ coordinate transactional work performed by the
+ resource managers and to drive two-phase and
+ recovery protocol. At the end of a transaction
+ (after a commit or rollback) the transaction manager
+ delists the resources.
+ </p>
+ <h5>
+ <a name="2pc" />
+ Two-Phase Commit
+ </h5>
+ <p>
+ This protocol between the transaction manager and
+ all the resources enlisted for a transaction ensures
+ that either all the resource managers commit the
+ transaction or they all abort. In this protocol,
+ when the application requests for committing the
+ transaction, the transaction manager issues a
+ prepare request to all the resource managers
+ involved. Each of these resources may in turn send a
+ reply indicating whether it is ready for commit or
+ not. Only The transaction manager issue a commit
+ request to all the resource managers, only when all
+ the resource managers are ready for a commit.
+ Otherwise, the transaction manager issues a rollback
+ request and the transaction will be rolled back.
+ </p>
+ <h5>
+ <a name="RecoveryLog" />
+ Recovery and Logging
+ </h5>
+ <div>
+ Basically, the Recovery is the mechanism which
+ preserves the transaction atomicity in presence of
+ failures. The basic technique for implementing
+ transactions in presence of failures is based on the
+ use of logs. That is, a transaction system has to
+ record enough information to ensure that it can be
+ able to return to a previous state in case of
+ failure or to ensure that changes committed by a
+ transaction are properly stored.
+ <p>
+ In addition to be able to store appropriate
+ information, all participants within a
+ distributed transaction must log similar
+ information which allow them to take a same
+ decision either to set data in their final state
+ or in their initial state.
+ </p>
+ <p>
+ Two techniques are in general used to ensure
+ transaction's atomicity. A first technique
+ focuses on manipulated data, such the
+ Do/Undo/Redo protocol (considered as a recovery
+ mechanism in a centralized system), which allow
+ a participant to set its data in their final
+ values or to retrieve them in their initial
+ values. A second technique relies on a
+ distributed protocol named the two phases
+ commit, ensuring that all participants involved
+ within a distributed transaction set their data
+ either in their final values or in their initial
+ values. In other words all participants must
+ commit or all must rollback.
+ </p>
+ <img border="0" src="includes/recovery_logs.GIF" />
+ <p />
+ <p>
+ In addition to failures we refer as centralized
+ such system crashes, communication failures due
+ for instance to
+ <span style="mso-spacerun:yes" />
+ network outages or message loss have to be
+ considered during the recovery process of a
+ distributed transaction.
+ </p>
+ <p>
+ In order to provide an efficient and optimized
+ mechanism to deal with failure, modern
+ transactional systems typically adopt a “presume
+ abort” strategy, which simplifies the
+ transaction management.
+ </p>
+ <p>
+ The presumed abort strategy can be stated as
+ «when in doubt, abort». With this strategy, when
+ the recovery mechanism has no information about
+ the transaction, it presumes that the
+ transaction has been aborted.
+ </p>
+ A particularity of the presumed-abort assumption
+ allows a coordinator to not log anything before the
+ commit decision and the participants do not to log
+ anything before they prepare. Then, any failure
+ which occurs before the 2pc starts lead to abort the
+ transaction. Furthermore, from a coordinator point
+ of view any communication failure detected by a
+ timeout or exception raised on sending prepare is
+ considered as a negative vote which leads to abort
+ the transaction. So, within a distributed
+ transaction a coordinator or a participant may fail
+ in two ways: either it crashes or it times out for a
+ message it was expecting. When a coordinator or a
+ participant crashes and then restarts, it uses
+ information on stable storage to determine the way
+ to perform the recovery. As we will see it the
+ presumed-abort strategy enable an optimized behavior
+ for the recovery.
+ </div>
+ <h5>Heuristic Decision</h5>
+ In extremely rare cases, a resource manager may choose
+ not to wait for the outcome from the transaction
+ manager. This might occur if the communications path was
+ lost and was not likely to be restored for a very long
+ time. Typically this happens as a result of human
+ intervention and not as an arbitrary action of a
+ resource manager. In order to release locks and make
+ this transactions data available to new transactions,
+ the resource manager makes a
+ <b>heuristic decision</b>
+ , i.e. it guesses the proper transaction outcome. When
+ it does so, it must remember its guess until contact
+ with the transaction manager is ultimately
+ re-established.
+ <h4>Standards</h4>
+ Saying that a distributed transaction can involve
+ several distributed participants, means that these
+ participant must be integrated within a global
+ transaction manager which has the responsibility to
+ ensure that all participants take a common decision to
+ commit or rollback the distributed transaction. The key
+ of such integration is the existence of a common
+ transactional interface which is understood by all
+ participants, transaction manager and resource managers
+ such databases.
+ <p>
+ The importance of common interfaces between
+ participants, as well as the complexity of their
+ implementation, becomes obvious in an open systems
+ environment. For this aim various distributed
+ transaction processing standards have been developed
+ by international standards organizations. Among
+ these organizations, We list three of them which are
+ mainly considered in the Jboss Transaction Service
+ product:
+ </p>
+ <ul>
+ <li>
+ The
+ <a class="linkscoloured"
+ href="xopen_overview.html">
+ X/Open model
+ </a>
+ and its successful XA interface
+ </li>
+ <li>
+ The OMG with its CORBA infrastructure and the
+ <a class="linkscoloured"
+ href="ots_overview.html">
+ Object Transaction Service
+ </a>
+ and finally
+ </li>
+ <li>
+ The Java Community Process leaded by Sun with
+ its
+ <a class="linkscoloured"
+ href="jta_overview.html">
+ JTA/JTS specification
+ </a>
+ </li>
+ </ul>
+ Basically these standards have proposed logical models,
+ which divide transaction processing into several
+ functions:
+ <ul>
+ <li>
+ those assigned to the application which ties
+ resources together in application- specific
+ operations
+ </li>
+ <li>
+ those assigned to the Resource manager which
+ access physically to data stores
+ </li>
+ <li>
+ functions performed by the Transaction Manager
+ which manages transactions, and finally
+ </li>
+ <li>
+ Communication Resource Managers which allow to
+ exchange information with other transactional
+ domains.
+ </li>
+ </ul>
+ <img border="0" src="includes/standards.GIF" />
+ </html>
+ </area>
+ </content>
+ <footer />
+</page>
Modified: labs/jbosstm/trunk/ArjunaJTS/trailmap/docs/part3.xml
===================================================================
--- labs/jbosstm/trunk/ArjunaJTS/trailmap/docs/part3.xml 2006-09-24 05:52:34 UTC (rev 6395)
+++ labs/jbosstm/trunk/ArjunaJTS/trailmap/docs/part3.xml 2006-09-24 07:16:18 UTC (rev 6396)
@@ -1,22 +1,180 @@
<?xml version="1.0"?>
<!--
- JBoss, Home of Professional Open Source
- Copyright 2006, JBoss Inc., and individual contributors as indicated
- by the @authors tag. All rights reserved.
- See the copyright.txt in the distribution for a full listing
- of individual contributors.
- This copyrighted material is made available to anyone wishing to use,
- modify, copy, or redistribute it subject to the terms and conditions
- of the GNU General Public License, v. 2.0.
- This program is distributed in the hope that it will be useful, but WITHOUT A
- WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS FOR A
- PARTICULAR PURPOSE. See the GNU General Public License for more details.
- You should have received a copy of the GNU General Public License,
- v. 2.0 along with this distribution; if not, write to the Free Software
- Foundation, Inc., 51 Franklin Street, Fifth Floor, Boston,
- MA 02110-1301, USA.
-
- (C) 2005-2006,
- @author JBoss Inc.
+ JBoss, Home of Professional Open Source
+ Copyright 2006, JBoss Inc., and individual contributors as indicated
+ by the @authors tag. All rights reserved.
+ See the copyright.txt in the distribution for a full listing
+ of individual contributors.
+ This copyrighted material is made available to anyone wishing to use,
+ modify, copy, or redistribute it subject to the terms and conditions
+ of the GNU General Public License, v. 2.0.
+ This program is distributed in the hope that it will be useful, but WITHOUT A
+ WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS FOR A
+ PARTICULAR PURPOSE. See the GNU General Public License for more details.
+ You should have received a copy of the GNU General Public License,
+ v. 2.0 along with this distribution; if not, write to the Free Software
+ Foundation, Inc., 51 Franklin Street, Fifth Floor, Boston,
+ MA 02110-1301, USA.
+
+ (C) 2005-2006,
+ @author JBoss Inc.
-->
-<page title="Arjuna Technologies Limited: Trail map: Overview of the Distributed Transaction Processing" rootpath="../.."> <header> Trail map: ArjunaTS Overview </header> <content> <navigation> <links include="includes/www_arjuna_com_navigation.xml"/> <links include="includes/trailmap_navigation.xml"/> <links title="Navigation"> <link ref="index.html">Home</link> <link ref="part2.html">Previous</link> <link ref="part4.html">Next</link> </links> <links include="includes/trailmap_additional.xml"/> </navigation> <area title="ArjunaTS Overview"> <html> <p>Arjuna Transaction Service 4.0 (ATS 4.0) assures complete, accurate business transactions for any Java based applications, including those written for the J2EE and EJB frameworks.</p> <p>ArjunaTS is a 100% Java implementation of a distributed transaction management system based on the Sun Microsystems J2EE Java Transaction Service (JTS) standard. Our imp!
lementation of the JTS utilizes the Object Management Group's (OMG) Object Transaction Service (OTS) model for transaction interoperability as recommended in the J2EE and EJB standards. Although any JTS-compliant product will allow Java objects to participate in transactions, one of the key features of ATS is it's 100% Java implementation. This allows ATS to support fully distributed transactions that can be coordinated by distributed parties. <p>ArjunaTS runs can be run both as an embedded distributed service of an application server (e.g., HPAS. JBoss), affording the user all the added benefits of the application server environment such as real-time load balancing, unlimited linear scalability and unmatched fault tolerance that allows you to deliver an always-on solution to your customers. It is also available as a free-standing Java Transaction Service.</p> <p>In addition to providing full compliance with the latest version of the JTS !
specification, ATS 4.0 leads the market in providing many advanced fea
tures such as fully distributed transactions and ORB portability with POA support.</p> <p>ATS 4.0 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>The Java Transaction API support for ATS comes in two flavours:</p> <ul> <li>a purely local implementation, that does not require an ORB, but obviously requires all coordinated resources to reside within the same JVM. </li> <li>a fully distributed implementation. </li> </ul> <h5>Key features</h5> <ul> <li>full compliant with the JTA 1.0.1 specification: <ul> <li>Purely local (ORB-less) JTA offers the fastest JTA performance </li> <li>JDBC 2.0 support </li> <li>XA compliance </li> <li>JDBC drivers for database access with full transaction support </li> <li>Automatic crash recovery f!
or XAResources </li> </ul> </li> <li>compliance with the JTS specification and OTS 1.2 specification from the OMG <ul> <li>Distributed JTA implementation </li> <li>support for distributed transactions (utilizing two-phase commit) </li> <li>POA ORB support </li> <li>interposition </li> <li>transaction heuristics</li> <li>distributed transaction manager (co-located with the transaction initiator) or transaction manager server </li> <li>checked/unchecked transaction behaviour </li> <li>supports both flat and nested transaction models, with nested-aware resources and resource adapters </li> <li>independent concurrency control system with support for type-specific concurrency control </li> <li>support for CosTransaction::Current </li> <li>direct and indirect transaction management </li> <li>synchronization interface </li> !
<li>explicit and implicit transaction context propagation </li>
<li>automatic crash recovery </li> <li>multi-thread aware </li> </ul> </li> <li>transactional objects (TO) for Java </li> <li>ORB independence via the ORB portability layer </li> </ul> </p> </html> </area> </content> <footer/> </page>
+<page
+ title="JBoss (a Division of Redhat): Trail map: Overview of the Distributed Transaction Processing"
+ rootpath="../..">
+ <header>Trail map: JBossTS Overview</header>
+ <content>
+ <navigation>
+ <links include="includes/www_arjuna_com_navigation.xml" />
+ <links include="includes/trailmap_navigation.xml" />
+ <links title="Navigation">
+ <link ref="index.html">Home</link>
+ <link ref="part2.html">Previous</link>
+ <link ref="part4.html">Next</link>
+ </links>
+ <links include="includes/trailmap_additional.xml" />
+ </navigation>
+ <area title="JBossTS Overview">
+ <html>
+ <p>
+ JBoss Transaction Service 4.0 (ATS 4.0) assures
+ complete, accurate business transactions for any
+ Java based applications, including those written for
+ the J2EE and EJB frameworks.
+ </p>
+ <p>
+ JBossTS is a 100% Java implementation of a
+ distributed transaction management system based on
+ the Sun Microsystems J2EE Java Transaction Service
+ (JTS) standard. Our implementation of the JTS
+ utilizes the Object Management Group's (OMG) Object
+ Transaction Service (OTS) model for transaction
+ interoperability as recommended in the J2EE and EJB
+ standards. Although any JTS-compliant product will
+ allow Java objects to participate in transactions,
+ one of the key features of ATS is it's 100% Java
+ implementation. This allows ATS to support fully
+ distributed transactions that can be coordinated by
+ distributed parties.
+ <p>
+ JBossTS runs can be run both as an embedded
+ distributed service of an application server
+ (e.g., HPAS. JBoss), affording the user all the
+ added benefits of the application server
+ environment such as real-time load balancing,
+ unlimited linear scalability and unmatched fault
+ tolerance that allows you to deliver an
+ always-on solution to your customers. It is also
+ available as a free-standing Java Transaction
+ Service.
+ </p>
+ <p>
+ In addition to providing full compliance with
+ the latest version of the JTS specification, ATS
+ 4.0 leads the market in providing many advanced
+ features such as fully distributed transactions
+ and ORB portability with POA support.
+ </p>
+ <p>
+ ATS 4.0 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>
+ The Java Transaction API support for ATS comes
+ in two flavours:
+ </p>
+ <ul>
+ <li>
+ a purely local implementation, that does not
+ require an ORB, but obviously requires all
+ coordinated resources to reside within the
+ same JVM.
+ </li>
+ <li>a fully distributed implementation.</li>
+ </ul>
+ <h5>Key features</h5>
+ <ul>
+ <li>
+ full compliant with the JTA 1.0.1
+ specification:
+ <ul>
+ <li>
+ Purely local (ORB-less) JTA offers
+ the fastest JTA performance
+ </li>
+ <li>JDBC 2.0 support</li>
+ <li>XA compliance</li>
+ <li>
+ JDBC drivers for database access
+ with full transaction support
+ </li>
+ <li>
+ Automatic crash recovery for
+ XAResources
+ </li>
+ </ul>
+ </li>
+ <li>
+ compliance with the JTS specification and
+ OTS 1.2 specification from the OMG
+ <ul>
+ <li>Distributed JTA implementation</li>
+ <li>
+ support for distributed transactions
+ (utilizing two-phase commit)
+ </li>
+ <li>POA ORB support</li>
+ <li>interposition</li>
+ <li>transaction heuristics</li>
+ <li>
+ distributed transaction manager
+ (co-located with the transaction
+ initiator) or transaction manager
+ server
+ </li>
+ <li>
+ checked/unchecked transaction
+ behaviour
+ </li>
+ <li>
+ supports both flat and nested
+ transaction models, with
+ nested-aware resources and resource
+ adapters
+ </li>
+ <li>
+ independent concurrency control
+ system with support for
+ type-specific concurrency control
+ </li>
+ <li>
+ support for CosTransaction::Current
+ </li>
+ <li>
+ direct and indirect transaction
+ management
+ </li>
+ <li>synchronization interface</li>
+ <li>
+ explicit and implicit transaction
+ context propagation
+ </li>
+ <li>automatic crash recovery</li>
+ <li>multi-thread aware</li>
+ </ul>
+ </li>
+ <li>transactional objects (TO) for Java</li>
+ <li>
+ ORB independence via the ORB portability
+ layer
+ </li>
+ </ul>
+ </p>
+ </html>
+ </area>
+ </content>
+ <footer />
+</page>
Modified: labs/jbosstm/trunk/ArjunaJTS/trailmap/docs/part5.xml
===================================================================
--- labs/jbosstm/trunk/ArjunaJTS/trailmap/docs/part5.xml 2006-09-24 05:52:34 UTC (rev 6395)
+++ labs/jbosstm/trunk/ArjunaJTS/trailmap/docs/part5.xml 2006-09-24 07:16:18 UTC (rev 6396)
@@ -1,51 +1,174 @@
<?xml version="1.0"?>
<!--
- JBoss, Home of Professional Open Source
- Copyright 2006, JBoss Inc., and individual contributors as indicated
- by the @authors tag. All rights reserved.
- See the copyright.txt in the distribution for a full listing
- of individual contributors.
- This copyrighted material is made available to anyone wishing to use,
- modify, copy, or redistribute it subject to the terms and conditions
- of the GNU General Public License, v. 2.0.
- This program is distributed in the hope that it will be useful, but WITHOUT A
- WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS FOR A
- PARTICULAR PURPOSE. See the GNU General Public License for more details.
- You should have received a copy of the GNU General Public License,
- v. 2.0 along with this distribution; if not, write to the Free Software
- Foundation, Inc., 51 Franklin Street, Fifth Floor, Boston,
- MA 02110-1301, USA.
-
- (C) 2005-2006,
- @author JBoss Inc.
+ JBoss, Home of Professional Open Source
+ Copyright 2006, JBoss Inc., and individual contributors as indicated
+ by the @authors tag. All rights reserved.
+ See the copyright.txt in the distribution for a full listing
+ of individual contributors.
+ This copyrighted material is made available to anyone wishing to use,
+ modify, copy, or redistribute it subject to the terms and conditions
+ of the GNU General Public License, v. 2.0.
+ This program is distributed in the hope that it will be useful, but WITHOUT A
+ WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS FOR A
+ PARTICULAR PURPOSE. See the GNU General Public License for more details.
+ You should have received a copy of the GNU General Public License,
+ v. 2.0 along with this distribution; if not, write to the Free Software
+ Foundation, Inc., 51 Franklin Street, Fifth Floor, Boston,
+ MA 02110-1301, USA.
+
+ (C) 2005-2006,
+ @author JBoss Inc.
-->
-<page title="Arjuna Technologies Limited: Trail map: Running and Testing Examples" rootpath="../.."> <header> Trail map: Running and Testing Examples </header> <content> <navigation> <links include="includes/www_arjuna_com_navigation.xml"/> <links include="includes/trailmap_navigation.xml"/> <links title="Navigation"> <link ref="index.html">Home</link> <link ref="part4.html">Previous</link> <link ref="part6.html">Next</link> </links> <links include="includes/trailmap_additional.xml"/> </navigation> <area title="Deploying and Testing The Banking Application"> <html> <p>Assuming that the Arjuna Transactioning product has been installed, this trail provides a set of examples that show how to build transactional applications. Two types of transactional applications are presented, those using the JTA interface and those accessing to the JTS (OTS) interfaces.</p> <p>Please follow these steps before running the tra!
nsactional applications</p> <ul> <li>Ensure you have the Ant build system installed. Ant is a Java build tool, similar to make. It is available for free from http://ant.apache.org/ The sample application requires version 1.5.1 or later. </li> <li>The PATH and CLASSPATH environment variables need to be set appropriately to use Arjuna 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 directory <font face="Courier New, Courier, mono"><arjunats_install_root>/bin/</font> </li> <li>From a command prompt, cd to the directory containing the build.xml file (<arjunats_install_root>/trail_map) and type 'ant', unless already done in the <a class="linkscoloured" href="part1.html#TestInstall">installation section</a> . This will compile a set of sources files located under <arjunats_install_root>/trail_map/src then crea!
te an application .jar file named <em>arjunats-demo.jar</em>. under
the directory <arjunats_install_root>/trail_map/lib</li> <li>Add the generated jar file to the CLASSPATH environment variable.</li> <li>The demo application is provided in several ways, accessing persistent data or not. When JDBC is used as a mean to access a database, Oracle 9i is used. For this aim the appropriate Oracle libraries (classes12.zip) should be add in the CLASSPATH environment variable.</li> </ul> <p>
-<h5>Local transaction with JTA</h5>
-To configure ATS for such transaction, edit the
-arjunajts-properties.xml file and set the following properties to the appropriate values:
+<page
+ title="JBoss (a Division of Redhat): Trail map: Running and Testing Examples"
+ rootpath="../..">
+ <header>Trail map: Running and Testing Examples</header>
+ <content>
+ <navigation>
+ <links include="includes/www_arjuna_com_navigation.xml" />
+ <links include="includes/trailmap_navigation.xml" />
+ <links title="Navigation">
+ <link ref="index.html">Home</link>
+ <link ref="part4.html">Previous</link>
+ <link ref="part6.html">Next</link>
+ </links>
+ <links include="includes/trailmap_additional.xml" />
+ </navigation>
+ <area title="Deploying and Testing The Banking Application">
+ <html>
+ <p>
+ Assuming that the JBoss Transactioning product has
+ been installed, this trail provides a set of
+ examples that show how to build transactional
+ applications. Two types of transactional
+ applications are presented, those using the JTA
+ interface and those accessing to the JTS (OTS)
+ interfaces.
+ </p>
+ <p>
+ Please follow these steps before running the
+ transactional applications
+ </p>
+ <ul>
+ <li>
+ Ensure you have the Ant build system installed.
+ Ant is a Java build tool, similar to make. It is
+ available for free from http://ant.apache.org/
+ The sample application requires version 1.5.1 or
+ later.
+ </li>
+ <li>
+ The PATH and CLASSPATH environment variables
+ need to be set appropriately to use Arjuna
+ 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
+ directory
+ <font face="Courier New, Courier, mono">
+ <jbossts_install_root>/bin/
+ </font>
+ </li>
+ <li>
+ From a command prompt, cd to the directory
+ containing the build.xml file
+ (<jbossts_install_root>/trail_map) and
+ type 'ant', unless already done in the
+ <a class="linkscoloured"
+ href="part1.html#TestInstall">
+ installation section
+ </a>
+ . This will compile a set of sources files
+ located under
+ <jbossts_install_root>/trail_map/src then
+ create an application .jar file named
+ <em>jbossts-demo.jar</em>
+ . under the directory
+ <jbossts_install_root>/trail_map/lib
+ </li>
+ <li>
+ Add the generated jar file to the CLASSPATH
+ environment variable.
+ </li>
+ <li>
+ The demo application is provided in several
+ ways, accessing persistent data or not. When
+ JDBC is used as a mean to access a database,
+ Oracle 9i is used. For this aim the appropriate
+ Oracle libraries (classes12.zip) should be add
+ in the CLASSPATH environment variable.
+ </li>
+ </ul>
+ <p>
+ <h5>Local transaction with JTA</h5>
+ To configure ATS for such transaction, edit the
+ arjunajts-properties.xml file and set the following
+ properties to the appropriate values:
-<pre>
- <property name="com.arjuna.ats.jta.jtaTMImplementation"
- value="com.arjuna.ats.internal.jta.transaction.
- arjunacore.TransactionManagerImple"/>
- <property name="com.arjuna.ats.jta.jtaUTImplementation"
- value="com.arjuna.ats.internal.jta.transaction.
- arjunacore.UserTransactionImple"/>
-</pre>
-<h5>Distributed transaction with JTA</h5>
-While for a distributed transactions case, ATS need to be configured as follow:
-<pre>
- <property name="com.arjuna.ats.jta.jtaTMImplementation"
- value="com.arjuna.ats.internal.jta.transaction.
- jts.TransactionManagerImple"/>
- <property name="com.arjuna.ats.jta.jtaUTImplementation"
- value="com.arjuna.ats.internal.jta.transaction.
- jts.UserTransactionImple"/>
-</pre>
+ <pre>
+ <property
+ name="com.arjuna.ats.jta.jtaTMImplementation"
+ value="com.arjuna.ats.internal.jta.transaction.
+ arjunacore.TransactionManagerImple"/>
+ <property
+ name="com.arjuna.ats.jta.jtaUTImplementation"
+ value="com.arjuna.ats.internal.jta.transaction.
+ arjunacore.UserTransactionImple"/>
+ </pre>
+ <h5>Distributed transaction with JTA</h5>
+ While for a distributed transactions case, ATS need
+ to be configured as follow:
+ <pre>
+ <property
+ name="com.arjuna.ats.jta.jtaTMImplementation"
+ value="com.arjuna.ats.internal.jta.transaction.
+ jts.TransactionManagerImple"/> <property
+ name="com.arjuna.ats.jta.jtaUTImplementation"
+ value="com.arjuna.ats.internal.jta.transaction.
+ jts.UserTransactionImple"/>
+ </pre>
-Using JTA to create a distributed transaction need the creation of an ORB instance as done by a JTS application
-(see JTS versions of the banking application), the difference is in the interface used to demarcate and control transactions.
+ Using JTA to create a distributed transaction need
+ the creation of an ORB instance as done by a JTS
+ application (see JTS versions of the banking
+ application), the difference is in the interface
+ used to demarcate and control transactions.
- </p>
+ </p>
-<h5>The application programming interfaces used by the Banking Application</h5> <p>To illustrate the programming interfaces possibilities enabled by ArjunaTS, the banking application is provided in several versions: a version that uses the JTA API and a second that uses JTS/OTS interfaces.</p> <p> This trail focuses to understanding concepts related to the creation of transactions and the behavior of the commitment protocol, while the next trail illustrates the similar application with persistent data.</p> <ul> <li> <a class="linkscoloured" href="part5_testing_jta.html">Testing the Banking application with JTA</a> </li> <li> <a class="linkscoloured" href="part5_testing_jts.html">Testing the Banking application with JTS</a> </li> </ul> </html> </area> </content> <footer/> </page>
+ <h5>
+ The application programming interfaces used by the
+ Banking Application
+ </h5>
+ <p>
+ To illustrate the programming interfaces
+ possibilities enabled by JBossTS, the banking
+ application is provided in several versions: a
+ version that uses the JTA API and a second that uses
+ JTS/OTS interfaces.
+ </p>
+ <p>
+ This trail focuses to understanding concepts related
+ to the creation of transactions and the behavior of
+ the commitment protocol, while the next trail
+ illustrates the similar application with persistent
+ data.
+ </p>
+ <ul>
+ <li>
+ <a class="linkscoloured"
+ href="part5_testing_jta.html">
+ Testing the Banking application with JTA
+ </a>
+ </li>
+ <li>
+ <a class="linkscoloured"
+ href="part5_testing_jts.html">
+ Testing the Banking application with JTS
+ </a>
+ </li>
+ </ul>
+ </html>
+ </area>
+ </content>
+ <footer />
+</page>
Modified: labs/jbosstm/trunk/ArjunaJTS/trailmap/docs/part5_jta.xml
===================================================================
--- labs/jbosstm/trunk/ArjunaJTS/trailmap/docs/part5_jta.xml 2006-09-24 05:52:34 UTC (rev 6395)
+++ labs/jbosstm/trunk/ArjunaJTS/trailmap/docs/part5_jta.xml 2006-09-24 07:16:18 UTC (rev 6396)
@@ -36,7 +36,7 @@
<p>From an architectural point of view of <a class="linkscoloured" href="JTA_Overview.html">JTA</a>, the bank client is considered as
an application program able to manage transactions via the <a class="linkscoloured" href="JTA_Overview.html#UserTransaction">javax.transaction.UserTransaction </a> interface. The following portion of code illustrates how a JTA transaction is
- started and terminated when the client asks to transfer money from one account to another. This also describes what are ArjunaTS packages that need to be used
+ started and terminated when the client asks to transfer money from one account to another. This also describes what are JBossTS packages that need to be used
in order to obtain appropriate objects instances (such UserTransaction).</p>
<p>Note: The code below is a simplified view of the BankClient.java program. Only the transfer operation is illustrated; other operations manage transactions in the same way.
(see for details the <a href="../src/com/arjuna/demo/jta/localbank/BankClient.java">BankClient.java</a>)</p>
Modified: labs/jbosstm/trunk/ArjunaJTS/trailmap/docs/part5_jts.xml
===================================================================
--- labs/jbosstm/trunk/ArjunaJTS/trailmap/docs/part5_jts.xml 2006-09-24 05:52:34 UTC (rev 6395)
+++ labs/jbosstm/trunk/ArjunaJTS/trailmap/docs/part5_jts.xml 2006-09-24 07:16:18 UTC (rev 6396)
@@ -42,7 +42,7 @@
done in the indirect mode. </p>
<p> The following portion of code illustrates how a JTS transaction is started
and terminated when the client asks to transfer money from one account to another.
- This also describes what are ArjunaTS packages that need to be used in order
+ This also describes what are JBossTS packages that need to be used in order
to obtain appropriate objects instances (such Current).</p>
<p>Note: The code below is a simplified view of the BankClient.java program. Only
the transfer operation is illustrated; other operations manage transactions
@@ -81,7 +81,7 @@
try
{
- //the following instruction asks a specific ArjunaTS class to obtain a Current instance
+ //the following instruction asks a specific JBossTS class to obtain a Current instance
<strong>Current current = OTSManager.get_current(); </strong>
System.out.println("Beginning a User transaction to get balance");
<strong>current.begin()</strong>;
@@ -108,7 +108,7 @@
myORB.initORB(args, null); //Initialise the ORB
myOA.initOA(); //Initialise the POA
- // The ORBManager is a class provided by ArjunaTS to facilitate the association
+ // The ORBManager is a class provided by JBossTS to facilitate the association
// of the ORB/POA with the transaction service
ORBManager.setORB(myORB);
ORBManager.setPOA(myOA);</strong>
Modified: labs/jbosstm/trunk/ArjunaJTS/trailmap/docs/part5_jts_explicit.xml
===================================================================
--- labs/jbosstm/trunk/ArjunaJTS/trailmap/docs/part5_jts_explicit.xml 2006-09-24 05:52:34 UTC (rev 6395)
+++ labs/jbosstm/trunk/ArjunaJTS/trailmap/docs/part5_jts_explicit.xml 2006-09-24 07:16:18 UTC (rev 6396)
@@ -81,7 +81,7 @@
<p>The following portion of code illustrates how a JTS transaction is started
and terminated when the client asks to transfer money from one account to another.
- This also describes what are ArjunaTS packages that need to be used in order
+ This also describes what are JBossTS packages that need to be used in order
to obtain appropriate objects instances (such Current).</p>
<p>Note: The code below is a simplified view of the BankClient.java program. Only
the transfer operation is illustrated; other operations manage transactions
@@ -104,7 +104,7 @@
try
{
//the following instruction asks a specific
- //ArjunaTS class to obtain a Current instance
+ //JBossTS class to obtain a Current instance
<strong>Current current = OTSManager.get_current(); </strong>
System.out.println("Beginning a User transaction to get balance");
<strong>current.begin()</strong>;
@@ -123,7 +123,7 @@
}</pre>
<p>Since JTS is used invocations against an ORB are needed, such ORB and Object
Adapter instantiation and initialisation. To ensure a better portability,
- the <a class="linkscoloured" href="ArjunaTS_ORBPortability.html"> ORB Portability API</a> provides a set of
+ the <a class="linkscoloured" href="JBossTS_ORBPortability.html"> ORB Portability API</a> provides a set of
methods that can be used as described below. </p>
<pre>public static void main( String [] args )
{
Modified: labs/jbosstm/trunk/ArjunaJTS/trailmap/docs/part5_jts_implicit.xml
===================================================================
--- labs/jbosstm/trunk/ArjunaJTS/trailmap/docs/part5_jts_implicit.xml 2006-09-24 05:52:34 UTC (rev 6395)
+++ labs/jbosstm/trunk/ArjunaJTS/trailmap/docs/part5_jts_implicit.xml 2006-09-24 07:16:18 UTC (rev 6396)
@@ -75,7 +75,7 @@
<p>The following portion of code illustrates how a JTS transaction is started
and terminated when the client asks to transfer money from one account to another.
- This also describes what are ArjunaTS packages that need to be used in order
+ This also describes what are JBossTS packages that need to be used in order
to obtain appropriate standard JTS API objects instances (such Current).</p>
<p>Note: The code below is a simplified view of the BankClient.java program. Only
the transfer operation is illustrated; other operations manage transactions
@@ -101,7 +101,7 @@
try
{
//the following instruction asks a
- // specific ArjunaTS class
+ // specific JBossTS class
// to obtain a Current instance
<strong>Current current = OTSManager.get_current(); </strong>
System.out.println("Beginning a User
@@ -122,7 +122,7 @@
}</pre>
<p>Since JTS is used invocations against an ORB are needed, such ORB and Object
Adapter instantiation and initialisation. To ensure a better portability,
- the <a class="linkscoloured" href="../html/ArjunaTS_ORBPortability.html"> ORB Portability API</a> provides a set of
+ the <a class="linkscoloured" href="../html/JBossTS_ORBPortability.html"> ORB Portability API</a> provides a set of
methods that can be used as described below. </p>
<pre>public static void main( String [] args )
{ ....
Modified: labs/jbosstm/trunk/ArjunaJTS/trailmap/docs/part5_jts_local.xml
===================================================================
--- labs/jbosstm/trunk/ArjunaJTS/trailmap/docs/part5_jts_local.xml 2006-09-24 05:52:34 UTC (rev 6395)
+++ labs/jbosstm/trunk/ArjunaJTS/trailmap/docs/part5_jts_local.xml 2006-09-24 07:16:18 UTC (rev 6396)
@@ -42,7 +42,7 @@
done in the indirect mode. </p>
<p> The following portion of code illustrates how a JTS transaction is started
and terminated when the client asks to transfer money from one account to another.
- This also describes what are ArjunaTS packages that need to be used in order
+ This also describes what are JBossTS packages that need to be used in order
to obtain appropriate objects instances (such Current).</p>
<p>Note: The code below is a simplified view of the BankClient.java program. Only
the transfer operation is illustrated; other operations manage transactions
@@ -84,7 +84,7 @@
try
{
//the following instruction asks a specific
- // ArjunaTS class to obtain a Current instance
+ // JBossTS class to obtain a Current instance
<strong>Current current = OTSManager.get_current(); </strong>
System.out.println("Beginning a User
transaction to get balance");
@@ -105,7 +105,7 @@
</pre>
<p>Since JTS is used invocations against an ORB are needed, such ORB and Object
Adapter instantiation and initialisation. To ensure a better portability,
- the <a class="linkscoloured" href="ArjunaTS_ORBPortability.html"> ORB Portability API</a> provides a set of
+ the <a class="linkscoloured" href="JBossTS_ORBPortability.html"> ORB Portability API</a> provides a set of
methods that can be used as described below. </p>
<pre>
public static void main( String [] args )
Modified: labs/jbosstm/trunk/ArjunaJTS/trailmap/docs/part5_testing_jta.xml
===================================================================
--- labs/jbosstm/trunk/ArjunaJTS/trailmap/docs/part5_testing_jta.xml 2006-09-24 05:52:34 UTC (rev 6395)
+++ labs/jbosstm/trunk/ArjunaJTS/trailmap/docs/part5_testing_jta.xml 2006-09-24 07:16:18 UTC (rev 6396)
@@ -19,7 +19,7 @@
(C) 2005-2006,
@author JBoss Inc.
-->
-<page title="Arjuna Technologies Limited: Trail map: Running and Testing Examples" rootpath="../..">
+<page title="JBoss (a Division of Redhat): Trail map: Running and Testing Examples" rootpath="../..">
<header> Trail map: Running and Testing Examples </header>
<content>
<navigation>
@@ -36,7 +36,7 @@
<h4>Configuring ATS</h4>
<p>Program Applications that create transactions using te JTA interface may invoke as well local services as remote
services. When a remote invocation need to be performed, the current transactional context need to be propagated
-to the remote service in order to involve it to the transaction in progress. Arjuna Transaction Service allows the
+to the remote service in order to involve it to the transaction in progress. JBoss Transaction Service allows the
possibility to provide such feature using the facilities provided by JTS and ORB. More precisely ATS need to be configured
to determine in which type of transaction, local or distributed, the JTA interface is used.
</p>
Modified: labs/jbosstm/trunk/ArjunaJTS/trailmap/docs/part5_testing_jts.xml
===================================================================
--- labs/jbosstm/trunk/ArjunaJTS/trailmap/docs/part5_testing_jts.xml 2006-09-24 05:52:34 UTC (rev 6395)
+++ labs/jbosstm/trunk/ArjunaJTS/trailmap/docs/part5_testing_jts.xml 2006-09-24 07:16:18 UTC (rev 6396)
@@ -35,12 +35,12 @@
<html>
<p>The JTS version of the Banking application means that the Object Request Broker
- will be used. The ArjunaTS distribution is provided to works with JacORB version
- 2.1 that can be obtained from the arjuna product page. ArjunaTS works also
+ 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>
-<p>To describe the possibilities provided by ArjunaTS to build a transactional
+<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>
<ul>
Modified: labs/jbosstm/trunk/ArjunaJTS/trailmap/docs/part5_testing_jtsDistributed.xml
===================================================================
--- labs/jbosstm/trunk/ArjunaJTS/trailmap/docs/part5_testing_jtsDistributed.xml 2006-09-24 05:52:34 UTC (rev 6395)
+++ labs/jbosstm/trunk/ArjunaJTS/trailmap/docs/part5_testing_jtsDistributed.xml 2006-09-24 07:16:18 UTC (rev 6396)
@@ -19,7 +19,7 @@
(C) 2005-2006,
@author JBoss Inc.
-->
-<page title="Arjuna Technologies Limited: Trail map: Running and Testing Examples" rootpath="../..">
+<page title="JBoss (a Division of Redhat): Trail map: Running and Testing Examples" rootpath="../..">
<header> Trail map: Running and Testing Examples </header>
<content>
<navigation>
@@ -34,13 +34,12 @@
<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 ArjunaTS distribution is provided to works with JacOrb version
- 2.1 that can be obtained from the <a class="linkscoloured" href="http://www.arjuna.com/products/arjunats/download/index.html">arjuna
- product page</a>.</p>
+ 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>
<p>
<strong>Note</strong>: Ensure that the jacorb jar files are added in your CLASSPATH</p>
<ul>
- <li>In a separate window launch the <a class="linkscoloured" href="ArjunaTS_Recovery.html">Recovery Manager</a>, as follow.</li>
+ <li>In a separate window launch the <a class="linkscoloured" href="JBossTS_Recovery.html">Recovery Manager</a>, as follow.</li>
</ul>
<blockquote>
<pre>java com.arjuna.ats.arjuna.recovery.RecoveryManager</pre>
@@ -149,7 +148,7 @@
minor code: 50001 completed: No</font>
</blockquote>
<h4>Using a stand-alone Transaction Server</h4>
- <p>By default ArjunaTS does not use a separate transaction manager server: transaction
+ <p>By default JBossTS does not use a separate transaction manager server: transaction
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
@@ -165,7 +164,7 @@
<area title="Running the example on several machines">
<html>
<p>
- It is possible to run the Arjuna Transaction Service and recovery manager processes on a different machine and have clients access these
+ It is possible to run the JBoss Transaction Service and recovery manager processes on a different machine and have clients access these
centralized services in a hub-and-spoke style architecture.</p>
<p>
All that must be done is to provide the clients with enough information to contact the transaction service (such as the ORB's NameService).
Modified: labs/jbosstm/trunk/ArjunaJTS/trailmap/docs/part5_testing_jtsLocal.xml
===================================================================
--- labs/jbosstm/trunk/ArjunaJTS/trailmap/docs/part5_testing_jtsLocal.xml 2006-09-24 05:52:34 UTC (rev 6395)
+++ labs/jbosstm/trunk/ArjunaJTS/trailmap/docs/part5_testing_jtsLocal.xml 2006-09-24 07:16:18 UTC (rev 6396)
@@ -34,9 +34,8 @@
<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 ArjunaTS distribution is provided to works with JacOrb version
- 2.1 that can be obtained from the <a class="linkscoloured" href="http://www.arjuna.com/products/arjunats/download/index.html">arjuna
- product page</a>.</p>
+ 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>
<p>
<strong>Note</strong>: Ensure that the jacorb jar files are added in your CLASSPATH</p>
@@ -129,7 +128,7 @@
</pre>
</blockquote>
<h4>Using a stand-alone Transaction Server</h4>
- <p>By default ArjunaTS does not use a separate transaction manager server: transaction
+ <p>By default JBossTS does not use a separate transaction manager server: transaction
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
Modified: labs/jbosstm/trunk/ArjunaJTS/trailmap/docs/part6.xml
===================================================================
--- labs/jbosstm/trunk/ArjunaJTS/trailmap/docs/part6.xml 2006-09-24 05:52:34 UTC (rev 6395)
+++ labs/jbosstm/trunk/ArjunaJTS/trailmap/docs/part6.xml 2006-09-24 07:16:18 UTC (rev 6396)
@@ -1,22 +1,100 @@
<?xml version="1.0"?>
<!--
- JBoss, Home of Professional Open Source
- Copyright 2006, JBoss Inc., and individual contributors as indicated
- by the @authors tag. All rights reserved.
- See the copyright.txt in the distribution for a full listing
- of individual contributors.
- This copyrighted material is made available to anyone wishing to use,
- modify, copy, or redistribute it subject to the terms and conditions
- of the GNU General Public License, v. 2.0.
- This program is distributed in the hope that it will be useful, but WITHOUT A
- WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS FOR A
- PARTICULAR PURPOSE. See the GNU General Public License for more details.
- You should have received a copy of the GNU General Public License,
- v. 2.0 along with this distribution; if not, write to the Free Software
- Foundation, Inc., 51 Franklin Street, Fifth Floor, Boston,
- MA 02110-1301, USA.
-
- (C) 2005-2006,
- @author JBoss Inc.
+ JBoss, Home of Professional Open Source
+ Copyright 2006, JBoss Inc., and individual contributors as indicated
+ by the @authors tag. All rights reserved.
+ See the copyright.txt in the distribution for a full listing
+ of individual contributors.
+ This copyrighted material is made available to anyone wishing to use,
+ modify, copy, or redistribute it subject to the terms and conditions
+ of the GNU General Public License, v. 2.0.
+ This program is distributed in the hope that it will be useful, but WITHOUT A
+ WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS FOR A
+ PARTICULAR PURPOSE. See the GNU General Public License for more details.
+ You should have received a copy of the GNU General Public License,
+ v. 2.0 along with this distribution; if not, write to the Free Software
+ Foundation, Inc., 51 Franklin Street, Fifth Floor, Boston,
+ MA 02110-1301, USA.
+
+ (C) 2005-2006,
+ @author JBoss Inc.
-->
-<page title="Arjuna Technologies Limited: Trail map: Running and Testing Examples" rootpath="../.."> <header> Making the Banking Application Persistent </header> <content> <navigation> <links include="includes/www_arjuna_com_navigation.xml"/> <links include="includes/trailmap_navigation.xml"/> <links title="Navigation"> <link ref="index.html">Home</link> <link ref="part5.html">Previous</link> <link ref="part7.html">Next</link> </links> <links include="includes/trailmap_additional.xml"/> </navigation> <area title="Making the Banking Application Persistent"> <html> <p>The way the banking application is built and deployed in the previous trail does not it make it persistent, in such way that any created account can be retrieved later after stopping the bank server or if the application crashes; moreover, it does not allow concurrent access to accounts without leading to inconsistent values.</p> <p>Two ways wil!
l be presented in this trail on the way to build the banking application as a persistent and sharable application:</p> <ul> <li>Using the Arjuna Transactional Object For Java (TXOJ) mechanisms <ul> <li> <a class="linkscoloured" href="part6_txoj_introduction.html"> Overview of the Transactional Object For Java</a> </li> <li> <a class="linkscoloured" href="part6_txoj_banking_deploy.html">Deploying the Banking application with TXOJ mechanisms</a> </li> </ul> </li> <li>Using the JDBC API by considering the banking application as a relational database. <ul> <li> <a class="linkscoloured" href="part6_jdbc_introduction.html">Developing applications with JDBC and ArjunaTA</a> </li> <li> <a class="linkscoloured" href="part6_jdbc_banking.html">The banking application as a relational database accessed with JDBC</a> </li> </ul> </li> </ul> </htm!
l> </area> </content> <footer/> </page>
+<page
+ title="JBoss (a Division of Redhat): Trail map: Running and Testing Examples"
+ rootpath="../..">
+ <header>Making the Banking Application Persistent</header>
+ <content>
+ <navigation>
+ <links include="includes/www_arjuna_com_navigation.xml" />
+ <links include="includes/trailmap_navigation.xml" />
+ <links title="Navigation">
+ <link ref="index.html">Home</link>
+ <link ref="part5.html">Previous</link>
+ <link ref="part7.html">Next</link>
+ </links>
+ <links include="includes/trailmap_additional.xml" />
+ </navigation>
+ <area title="Making the Banking Application Persistent">
+ <html>
+ <p>
+ The way the banking application is built and
+ deployed in the previous trail does not it make it
+ persistent, in such way that any created account can
+ be retrieved later after stopping the bank server or
+ if the application crashes; moreover, it does not
+ allow concurrent access to accounts without leading
+ to inconsistent values.
+ </p>
+ <p>
+ Two ways will be presented in this trail on the way
+ to build the banking application as a persistent and
+ sharable application:
+ </p>
+ <ul>
+ <li>
+ Using the JBoss Transactional Object For Java
+ (TXOJ) mechanisms
+ <ul>
+ <li>
+ <a class="linkscoloured"
+ href="part6_txoj_introduction.html">
+ Overview of the Transactional Object
+ For Java
+ </a>
+ </li>
+ <li>
+ <a class="linkscoloured"
+ href="part6_txoj_banking_deploy.html">
+ Deploying the Banking application
+ with TXOJ mechanisms
+ </a>
+ </li>
+ </ul>
+ </li>
+ <li>
+ Using the JDBC API by considering the banking
+ application as a relational database.
+ <ul>
+ <li>
+ <a class="linkscoloured"
+ href="part6_jdbc_introduction.html">
+ Developing applications with JDBC
+ and ArjunaTA
+ </a>
+ </li>
+ <li>
+ <a class="linkscoloured"
+ href="part6_jdbc_banking.html">
+ The banking application as a
+ relational database accessed with
+ JDBC
+ </a>
+ </li>
+ </ul>
+ </li>
+ </ul>
+ </html>
+ </area>
+ </content>
+ <footer />
+</page>
Modified: labs/jbosstm/trunk/ArjunaJTS/trailmap/docs/part6_txoj_banking_deploy.xml
===================================================================
--- labs/jbosstm/trunk/ArjunaJTS/trailmap/docs/part6_txoj_banking_deploy.xml 2006-09-24 05:52:34 UTC (rev 6395)
+++ labs/jbosstm/trunk/ArjunaJTS/trailmap/docs/part6_txoj_banking_deploy.xml 2006-09-24 07:16:18 UTC (rev 6396)
@@ -42,9 +42,8 @@
<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 ArjunaTS distribution is provided to works with JacOrb version 2.1
- that can be obtained from the <a class="linkscoloured" href="http://www.arjuna.com/products/arjunats/download/index.html">arjuna
- product page</a>.</p>
+ 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>
<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 2006-09-24 05:52:34 UTC (rev 6395)
+++ labs/jbosstm/trunk/ArjunaJTS/trailmap/docs/part7.xml 2006-09-24 07:16:18 UTC (rev 6396)
@@ -19,7 +19,7 @@
(C) 2005-2006,
@author JBoss Inc.
-->
-<page title="Arjuna Technologies Limited: Trail map: Running and Testing Examples" rootpath="../..">
+<page title="JBoss (a Division of Redhat): Trail map: Running and Testing Examples" rootpath="../..">
<header> Recovery From Failure </header>
<content>
<navigation>
@@ -62,13 +62,13 @@
<p>
<i>This section provides only brief information on running the recovery manager from provided scripts.
For complete information on the recovery manager (including how to configure it), click
- <a class="linkscoloured" href="ArjunaTS_Recovery.html">here</a>.</i></p>
+ <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>
<ol>
<li>Open a command prompt</li>
- <li>cd to the directory <font face="Courier New, Courier, mono"><arjunats_install_root>\services\bin\windows</font></li>
+ <li>cd to the directory <font face="Courier New, Courier, mono"><jbossts_install_root>\services\bin\windows</font></li>
<li>Type <font face="Courier New, Courier, mono">InstallRecoveryManagerService-NT.bat</font></li>
</ol>
<p>
@@ -77,7 +77,7 @@
To launch the Recovery Manager as a Windows process, simply:</p>
<ol>
<li>Open a command prompt</li>
- <li>cd to the directory <font face="Courier New, Courier, mono"><arjunats_install_root>\services\bin\windows</font></li>
+ <li>cd to the directory <font face="Courier New, Courier, mono"><jbossts_install_root>\services\bin\windows</font></li>
<li>Type <font face="Courier New, Courier, mono">recoverymanagerservice.bat</font></li>
</ol>
<h4>UNIX</h4>
@@ -85,7 +85,7 @@
To launch the Recovery Manager on a UNIX platform, simply:</p>
<ol>
<li>Open a command prompt</li>
- <li>cd to the directory <font face="Courier New, Courier, mono"><arjunats_install_root>\services\bin\[platform]</font></li>
+ <li>cd to the directory <font face="Courier New, Courier, mono"><jbossts_install_root>\services\bin\[platform]</font></li>
<li>Type <font face="Courier New, Courier, mono">recoverymanagerservice.sh start</font></li>
</ol>
<p>
@@ -164,7 +164,7 @@
<h4>Specify the transaction manager type to use</h4>
<p>
- The recovery manager will work in the same manner for either the JTA or JTS implementation. By default the Arjuna Transaction Service
+ 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
the ATS transaction manager to use JTA rather than JTS.</i></p>
@@ -184,7 +184,7 @@
<p>To launch the Test Recovery Module, execute the following java program</p>
<ol>
<li>Open a command prompt</li>
- <li>cd to the directory <font face="Courier New, Courier, mono"><arjunats_install_root>\trail_map</font></li>
+ <li>cd to the directory <font face="Courier New, Courier, mono"><jbossts_install_root>\trail_map</font></li>
<li>Type <font face="Courier New, Courier, mono">java com.arjuna.demo.recovery.xaresource.TestXAResourceRecovery</font></li>
<li>View the output noting the crash during commit.</li>
<li>Inspect the current working directory to note that the applications have created several log files which you may like to review.</li>
@@ -201,7 +201,7 @@
<html>
<p>
<b>WARNING: Implementing a RecoveryModule and AbstractRecord is a very advanced feature of the transaction service. It should only
- be performed by users familiar with the all the concepts used in the Arjuna Transactions product. Please see the ArjunaCore guide for more
+ be performed by users familiar with the all the concepts used in the JBoss Transactions product. Please see the ArjunaCore guide for more
information about RecoveryModules and AbstractRecords.</b></p>
<p>
The following sample gives an overview how the Recovery Manager invokes a module to recover from failure.
@@ -248,7 +248,7 @@
Where <i> represent the new occurrence number that follows the last that already exists in the file. Once started, the Recovery Manager will automatically load the added Recovery module.
<h4>Starting the Recovery Manager</h4>
- In a separate window launch the <a class="linkscoloured" href="ArjunaTS_Recovery.html">Recovery Manager</a>,
+ In a separate window launch the <a class="linkscoloured" href="JBossTS_Recovery.html">Recovery Manager</a>,
as follow.
<pre>java com.arjuna.ats.arjuna.recovery.RecoveryManager -test</pre>
Modified: labs/jbosstm/trunk/ArjunaJTS/trailmap/src/com/arjuna/demo/jta/jdbcbank/Bank.java
===================================================================
--- labs/jbosstm/trunk/ArjunaJTS/trailmap/src/com/arjuna/demo/jta/jdbcbank/Bank.java 2006-09-24 05:52:34 UTC (rev 6395)
+++ labs/jbosstm/trunk/ArjunaJTS/trailmap/src/com/arjuna/demo/jta/jdbcbank/Bank.java 2006-09-24 07:16:18 UTC (rev 6396)
@@ -39,7 +39,7 @@
/**
- * This is the JDBC implementation of the Bank class used in the Arjuna Transactions product trailmap. It is used to
+ * This is the JDBC implementation of the Bank class used in the JBoss Transactions product trailmap. It is used to
* create and clean the database that the example uses as well as perform the banking operations that all Bank
* implementations in the trailmap provide, such as creating and accessing an account.
*/
Modified: labs/jbosstm/trunk/ArjunaJTS/trailmap/src/com/arjuna/demo/jta/jdbcbank/BankClient.java
===================================================================
--- labs/jbosstm/trunk/ArjunaJTS/trailmap/src/com/arjuna/demo/jta/jdbcbank/BankClient.java 2006-09-24 05:52:34 UTC (rev 6395)
+++ labs/jbosstm/trunk/ArjunaJTS/trailmap/src/com/arjuna/demo/jta/jdbcbank/BankClient.java 2006-09-24 07:16:18 UTC (rev 6396)
@@ -37,7 +37,7 @@
import java.util.Hashtable;
/**
- * The <CODE>BankClient</CODE> application is an interactive CLI that allows the user of the Arjuna Transactions product
+ * The <CODE>BankClient</CODE> application is an interactive CLI that allows the user of the JBoss Transactions product
* to manipulate a database backed bank under transactional control.
*/
public class BankClient
@@ -508,7 +508,7 @@
}
/**
- * This is the entry point into the Arjuna Transaction product trailmap sample that uses a JDBC database to store
+ * This is the entry point into the JBoss Transaction product trailmap sample that uses a JDBC database to store
* the bank accounts repository. At minimum it should be invoked with the "-host [db_host] -port [db_port]" flags.
*
* @param args The arguments to configure this run of the JDBC backed trailmap example
Modified: labs/jbosstm/trunk/ArjunaJTS/trailmap/src/com/arjuna/demo/jta/localbank/Account.java
===================================================================
--- labs/jbosstm/trunk/ArjunaJTS/trailmap/src/com/arjuna/demo/jta/localbank/Account.java 2006-09-24 05:52:34 UTC (rev 6395)
+++ labs/jbosstm/trunk/ArjunaJTS/trailmap/src/com/arjuna/demo/jta/localbank/Account.java 2006-09-24 07:16:18 UTC (rev 6396)
@@ -98,7 +98,7 @@
* Get access to the XA resource. The XA resource is the workhorse part of the account object. The tutorial provides
* a sample XA-aware non-persistent object that can be used to manage an account transactionally.
*
- * @return The Arjuna Transactions product sample XA resource.
+ * @return The JBoss Transactions product sample XA resource.
*
* @throws SystemException If the current transaction cannot be obtained.
* @throws RollbackException If the account is tried to be used after its transaction is marked for rollback.
Modified: labs/jbosstm/trunk/ArjunaJTS/trailmap/src/com/arjuna/demo/jta/localbank/Bank.java
===================================================================
--- labs/jbosstm/trunk/ArjunaJTS/trailmap/src/com/arjuna/demo/jta/localbank/Bank.java 2006-09-24 05:52:34 UTC (rev 6395)
+++ labs/jbosstm/trunk/ArjunaJTS/trailmap/src/com/arjuna/demo/jta/localbank/Bank.java 2006-09-24 07:16:18 UTC (rev 6396)
@@ -28,7 +28,7 @@
package com.arjuna.demo.jta.localbank;
/**
- * This is the in memory implementation of the Bank class used in the Arjuna Transactions product trailmap. As it is
+ * This is the in memory implementation of the Bank class used in the JBoss Transactions product trailmap. As it is
* non-persistent, it is only used to perform the banking operations that all Bank implementations in the trailmap
* provide, such as creating and accessing an account.
*/
Modified: labs/jbosstm/trunk/ArjunaJTS/trailmap/src/com/arjuna/demo/jta/localbank/BankClient.java
===================================================================
--- labs/jbosstm/trunk/ArjunaJTS/trailmap/src/com/arjuna/demo/jta/localbank/BankClient.java 2006-09-24 05:52:34 UTC (rev 6395)
+++ labs/jbosstm/trunk/ArjunaJTS/trailmap/src/com/arjuna/demo/jta/localbank/BankClient.java 2006-09-24 07:16:18 UTC (rev 6396)
@@ -30,7 +30,7 @@
import java.io.IOException;
/**
- * The <CODE>BankClient</CODE> application is an interactive CLI that allows the user of the Arjuna Transactions product
+ * The <CODE>BankClient</CODE> application is an interactive CLI that allows the user of the JBoss Transactions product
* to manipulate a volatile hashtable-backed <CODE>Bank</CODE> under transactional control.
*/
public class BankClient
@@ -508,7 +508,7 @@
/**
- * This is the entry point into the Arjuna Transaction product trailmap sample that uses a <CODE>Hashtable</CODE> to
+ * This is the entry point into the JBoss Transaction product trailmap sample that uses a <CODE>Hashtable</CODE> to
* store the bank accounts repository. It is part of the JTA trailmap when using local objects.
*
* @param args Not used in this example.
Modified: labs/jbosstm/trunk/ArjunaJTS/trailmap/src/com/arjuna/demo/jts/explicitremotebank/AccountResource.java
===================================================================
--- labs/jbosstm/trunk/ArjunaJTS/trailmap/src/com/arjuna/demo/jts/explicitremotebank/AccountResource.java 2006-09-24 05:52:34 UTC (rev 6395)
+++ labs/jbosstm/trunk/ArjunaJTS/trailmap/src/com/arjuna/demo/jts/explicitremotebank/AccountResource.java 2006-09-24 07:16:18 UTC (rev 6396)
@@ -28,7 +28,7 @@
package com.arjuna.demo.jts.explicitremotebank;
/**
- * The AccountResource shows a sample ResourcePOA implementation. It is provided as part of the Arjuna Transactions
+ * The AccountResource shows a sample ResourcePOA implementation. It is provided as part of the JBoss Transactions
* product trailmap showing a sample bank application built using JTS.
*
* Although the class does not demonstrate it, of particular interest is the Heuristic exceptions that may be raised
Modified: labs/jbosstm/trunk/ArjunaJTS/trailmap/src/com/arjuna/demo/jts/explicitremotebank/BankClient.java
===================================================================
--- labs/jbosstm/trunk/ArjunaJTS/trailmap/src/com/arjuna/demo/jts/explicitremotebank/BankClient.java 2006-09-24 05:52:34 UTC (rev 6395)
+++ labs/jbosstm/trunk/ArjunaJTS/trailmap/src/com/arjuna/demo/jts/explicitremotebank/BankClient.java 2006-09-24 07:16:18 UTC (rev 6396)
@@ -36,7 +36,7 @@
import java.io.IOException;
/**
- * The <CODE>BankClient</CODE> application is an interactive CLI that allows the user of the Arjuna Transactions product
+ * The <CODE>BankClient</CODE> application is an interactive CLI that allows the user of the JBoss Transactions product
* to manipulate a database backed bank under transactional control.
*/
public class BankClient
@@ -447,19 +447,19 @@
*/
public static void main(String[] args)
{
- // Define an ORB suitable for use by the Arjuna Transactions product ORB portability layer.
+ // Define an ORB suitable for use by the JBoss Transactions product ORB portability layer.
ORB myORB = null;
- // Define an object adapter suitable for use by the Arjuna Transactions product ORB portability layer.
+ // Define an object adapter suitable for use by the JBoss Transactions product ORB portability layer.
RootOA myOA = null;
try
{
- // Initialize the ORB reference using the Arjuna Transactions product ORB portability layer.
+ // Initialize the ORB reference using the JBoss Transactions product ORB portability layer.
myORB = ORB.getInstance("ClientSide");
- // Initialize the object adapter reference using the Arjuna Transactions product ORB portability layer.
+ // Initialize the object adapter reference using the JBoss Transactions product ORB portability layer.
myOA = OA.getRootOA(myORB);
- // Initialize the ORB using the Arjuna Transactions product ORB portability layer.
+ // Initialize the ORB using the JBoss Transactions product ORB portability layer.
myORB.initORB(args, null);
- // Initialize the object adapter reference using the Arjuna Transactions product ORB portability layer.
+ // Initialize the object adapter reference using the JBoss Transactions product ORB portability layer.
myOA.initOA();
}
catch (Exception e)
@@ -472,7 +472,7 @@
}
// Obtain a reference to the BankImpl CORBA representation inorder to be able to use it to transactionally
- // invoke banking operations as part of the Arjuna Transactions product trailmap
+ // invoke banking operations as part of the JBoss Transactions product trailmap
// Define the reference to invoke
Bank bank = null;
// Obtain the reference for bank
Modified: labs/jbosstm/trunk/ArjunaJTS/trailmap/src/com/arjuna/demo/jts/explicitremotebank/BankImpl.java
===================================================================
--- labs/jbosstm/trunk/ArjunaJTS/trailmap/src/com/arjuna/demo/jts/explicitremotebank/BankImpl.java 2006-09-24 05:52:34 UTC (rev 6395)
+++ labs/jbosstm/trunk/ArjunaJTS/trailmap/src/com/arjuna/demo/jts/explicitremotebank/BankImpl.java 2006-09-24 07:16:18 UTC (rev 6396)
@@ -30,7 +30,7 @@
import com.arjuna.orbportability.OA;
/**
- * This is an in memory, remotely available implementation of the Bank class used in the Arjuna Transactions product
+ * This is an in memory, remotely available implementation of the Bank class used in the JBoss Transactions product
* trailmap. As it is non-persistent, it is only used to perform the banking operations that all Bank implementations in
* the trailmap provide, such as creating and accessing an account, though it is a CORBA object and as such can be
* remotely accessed.
Modified: labs/jbosstm/trunk/ArjunaJTS/trailmap/src/com/arjuna/demo/jts/explicitremotebank/BankServer.java
===================================================================
--- labs/jbosstm/trunk/ArjunaJTS/trailmap/src/com/arjuna/demo/jts/explicitremotebank/BankServer.java 2006-09-24 05:52:34 UTC (rev 6395)
+++ labs/jbosstm/trunk/ArjunaJTS/trailmap/src/com/arjuna/demo/jts/explicitremotebank/BankServer.java 2006-09-24 07:16:18 UTC (rev 6396)
@@ -47,19 +47,19 @@
public static void main(String[] args)
{
// 0. Define and create the ORB
- // Define an ORB suitable for use by the Arjuna Transactions product ORB portability layer.
+ // Define an ORB suitable for use by the JBoss Transactions product ORB portability layer.
ORB myORB = null;
- // Define an object adapter suitable for use by the Arjuna Transactions product ORB portability layer.
+ // Define an object adapter suitable for use by the JBoss Transactions product ORB portability layer.
RootOA myOA = null;
try
{
- // Initialize the ORB reference using the Arjuna Transactions product ORB portability layer.
+ // Initialize the ORB reference using the JBoss Transactions product ORB portability layer.
myORB = ORB.getInstance("ServerSide");
- // Initialize the object adapter reference using the Arjuna Transactions product ORB portability layer.
+ // Initialize the object adapter reference using the JBoss Transactions product ORB portability layer.
myOA = OA.getRootOA(myORB);
- // Initialize the ORB using the Arjuna Transactions product ORB portability layer.
+ // Initialize the ORB using the JBoss Transactions product ORB portability layer.
myORB.initORB(args, null);
- // Initialize the object adapter reference using the Arjuna Transactions product ORB portability layer.
+ // Initialize the object adapter reference using the JBoss Transactions product ORB portability layer.
myOA.initOA();
}
catch (Exception e)
Modified: labs/jbosstm/trunk/ArjunaJTS/trailmap/src/com/arjuna/demo/jts/localbank/AccountResource.java
===================================================================
--- labs/jbosstm/trunk/ArjunaJTS/trailmap/src/com/arjuna/demo/jts/localbank/AccountResource.java 2006-09-24 05:52:34 UTC (rev 6395)
+++ labs/jbosstm/trunk/ArjunaJTS/trailmap/src/com/arjuna/demo/jts/localbank/AccountResource.java 2006-09-24 07:16:18 UTC (rev 6396)
@@ -28,7 +28,7 @@
package com.arjuna.demo.jts.localbank;
/**
- * The AccountResource shows a sample ResourcePOA implementation. It is provided as part of the Arjuna Transactions
+ * The AccountResource shows a sample ResourcePOA implementation. It is provided as part of the JBoss Transactions
* product trailmap showing a sample bank application built using JTS.
*
* Although the class does not demonstrate it, of particular interest is the Heuristic exceptions that may be raised
Modified: labs/jbosstm/trunk/ArjunaJTS/trailmap/src/com/arjuna/demo/jts/localbank/Bank.java
===================================================================
--- labs/jbosstm/trunk/ArjunaJTS/trailmap/src/com/arjuna/demo/jts/localbank/Bank.java 2006-09-24 05:52:34 UTC (rev 6395)
+++ labs/jbosstm/trunk/ArjunaJTS/trailmap/src/com/arjuna/demo/jts/localbank/Bank.java 2006-09-24 07:16:18 UTC (rev 6396)
@@ -28,7 +28,7 @@
package com.arjuna.demo.jts.localbank;
/**
- * This is an in memory implementation of the Bank class used in the Arjuna Transactions product trailmap. As it is
+ * This is an in memory implementation of the Bank class used in the JBoss Transactions product trailmap. As it is
* non-persistent, it is only used to perform the banking operations that all Bank implementations in the trailmap
* provide, such as creating and accessing an account.
*/
Modified: labs/jbosstm/trunk/ArjunaJTS/trailmap/src/com/arjuna/demo/jts/localbank/BankClient.java
===================================================================
--- labs/jbosstm/trunk/ArjunaJTS/trailmap/src/com/arjuna/demo/jts/localbank/BankClient.java 2006-09-24 05:52:34 UTC (rev 6395)
+++ labs/jbosstm/trunk/ArjunaJTS/trailmap/src/com/arjuna/demo/jts/localbank/BankClient.java 2006-09-24 07:16:18 UTC (rev 6396)
@@ -36,7 +36,7 @@
import java.io.IOException;
/**
- * The <CODE>BankClient</CODE> application is an interactive CLI that allows the user of the Arjuna Transactions product
+ * The <CODE>BankClient</CODE> application is an interactive CLI that allows the user of the JBoss Transactions product
* to manipulate a database backed bank under transactional control.
*/
public class BankClient
@@ -440,26 +440,26 @@
}
/**
- * This is the entry point into the Arjuna Transaction product trailmap sample that uses a <CODE>Hashtable</CODE> to
+ * This is the entry point into the JBoss Transaction product trailmap sample that uses a <CODE>Hashtable</CODE> to
* store the bank accounts repository. It is part of the JTS trailmap when using local objects.
*
* @param args Not used in this example.
*/
public static void main(String[] args)
{
- // Define an ORB suitable for use by the Arjuna Transactions product ORB portability layer.
+ // Define an ORB suitable for use by the JBoss Transactions product ORB portability layer.
ORB myORB = null;
- // Define an object adapter suitable for use by the Arjuna Transactions product ORB portability layer.
+ // Define an object adapter suitable for use by the JBoss Transactions product ORB portability layer.
RootOA myOA = null;
try
{
- // Initialize the ORB reference using the Arjuna Transactions product ORB portability layer.
+ // Initialize the ORB reference using the JBoss Transactions product ORB portability layer.
myORB = ORB.getInstance("test");
- // Initialize the object adapter reference using the Arjuna Transactions product ORB portability layer.
+ // Initialize the object adapter reference using the JBoss Transactions product ORB portability layer.
myOA = OA.getRootOA(myORB);
- // Initialize the ORB using the Arjuna Transactions product ORB portability layer.
+ // Initialize the ORB using the JBoss Transactions product ORB portability layer.
myORB.initORB(args, null);
- // Initialize the object adapter reference using the Arjuna Transactions product ORB portability layer.
+ // Initialize the object adapter reference using the JBoss Transactions product ORB portability layer.
myOA.initOA();
}
catch (Exception e)
Modified: labs/jbosstm/trunk/ArjunaJTS/trailmap/src/com/arjuna/demo/jts/remotebank/AccountResource.java
===================================================================
--- labs/jbosstm/trunk/ArjunaJTS/trailmap/src/com/arjuna/demo/jts/remotebank/AccountResource.java 2006-09-24 05:52:34 UTC (rev 6395)
+++ labs/jbosstm/trunk/ArjunaJTS/trailmap/src/com/arjuna/demo/jts/remotebank/AccountResource.java 2006-09-24 07:16:18 UTC (rev 6396)
@@ -28,7 +28,7 @@
package com.arjuna.demo.jts.remotebank;
/**
- * The AccountResource shows a sample ResourcePOA implementation. It is provided as part of the Arjuna Transactions
+ * The AccountResource shows a sample ResourcePOA implementation. It is provided as part of the JBoss Transactions
* product trailmap showing a sample bank application built using JTS.
*
* Although the class does not demonstrate it, of particular interest is the Heuristic exceptions that may be raised
Modified: labs/jbosstm/trunk/ArjunaJTS/trailmap/src/com/arjuna/demo/jts/remotebank/BankClient.java
===================================================================
--- labs/jbosstm/trunk/ArjunaJTS/trailmap/src/com/arjuna/demo/jts/remotebank/BankClient.java 2006-09-24 05:52:34 UTC (rev 6395)
+++ labs/jbosstm/trunk/ArjunaJTS/trailmap/src/com/arjuna/demo/jts/remotebank/BankClient.java 2006-09-24 07:16:18 UTC (rev 6396)
@@ -36,7 +36,7 @@
import java.io.IOException;
/**
- * The <CODE>BankClient</CODE> application is an interactive CLI that allows the user of the Arjuna Transactions product
+ * The <CODE>BankClient</CODE> application is an interactive CLI that allows the user of the JBoss Transactions product
* to manipulate a database backed bank under transactional control.
*/
public class BankClient
@@ -447,19 +447,19 @@
*/
public static void main(String[] args)
{
- // Define an ORB suitable for use by the Arjuna Transactions product ORB portability layer.
+ // Define an ORB suitable for use by the JBoss Transactions product ORB portability layer.
ORB myORB = null;
- // Define an object adapter suitable for use by the Arjuna Transactions product ORB portability layer.
+ // Define an object adapter suitable for use by the JBoss Transactions product ORB portability layer.
RootOA myOA = null;
try
{
- // Initialize the ORB reference using the Arjuna Transactions product ORB portability layer.
+ // Initialize the ORB reference using the JBoss Transactions product ORB portability layer.
myORB = ORB.getInstance("ClientSide");
- // Initialize the object adapter reference using the Arjuna Transactions product ORB portability layer.
+ // Initialize the object adapter reference using the JBoss Transactions product ORB portability layer.
myOA = OA.getRootOA(myORB);
- // Initialize the ORB using the Arjuna Transactions product ORB portability layer.
+ // Initialize the ORB using the JBoss Transactions product ORB portability layer.
myORB.initORB(args, null);
- // Initialize the object adapter reference using the Arjuna Transactions product ORB portability layer.
+ // Initialize the object adapter reference using the JBoss Transactions product ORB portability layer.
myOA.initOA();
}
catch (Exception e)
@@ -472,7 +472,7 @@
}
// Obtain a reference to the BankImpl CORBA representation inorder to be able to use it to transactionally
- // invoke banking operations as part of the Arjuna Transactions product trailmap
+ // invoke banking operations as part of the JBoss Transactions product trailmap
// Define the reference to invoke
Bank bank = null;
// Obtain the reference for bank
Modified: labs/jbosstm/trunk/ArjunaJTS/trailmap/src/com/arjuna/demo/jts/remotebank/BankImpl.java
===================================================================
--- labs/jbosstm/trunk/ArjunaJTS/trailmap/src/com/arjuna/demo/jts/remotebank/BankImpl.java 2006-09-24 05:52:34 UTC (rev 6395)
+++ labs/jbosstm/trunk/ArjunaJTS/trailmap/src/com/arjuna/demo/jts/remotebank/BankImpl.java 2006-09-24 07:16:18 UTC (rev 6396)
@@ -30,7 +30,7 @@
import com.arjuna.orbportability.OA;
/**
- * This is an in memory, remotely available implementation of the Bank class used in the Arjuna Transactions product
+ * This is an in memory, remotely available implementation of the Bank class used in the JBoss Transactions product
* trailmap. As it is non-persistent, it is only used to perform the banking operations that all Bank implementations in
* the trailmap provide, such as creating and accessing an account, though it is a CORBA object and as such can be
* remotely accessed.
Modified: labs/jbosstm/trunk/ArjunaJTS/trailmap/src/com/arjuna/demo/jts/remotebank/BankServer.java
===================================================================
--- labs/jbosstm/trunk/ArjunaJTS/trailmap/src/com/arjuna/demo/jts/remotebank/BankServer.java 2006-09-24 05:52:34 UTC (rev 6395)
+++ labs/jbosstm/trunk/ArjunaJTS/trailmap/src/com/arjuna/demo/jts/remotebank/BankServer.java 2006-09-24 07:16:18 UTC (rev 6396)
@@ -47,19 +47,19 @@
public static void main(String[] args)
{
// 0. Define and create the ORB
- // Define an ORB suitable for use by the Arjuna Transactions product ORB portability layer.
+ // Define an ORB suitable for use by the JBoss Transactions product ORB portability layer.
ORB myORB = null;
- // Define an object adapter suitable for use by the Arjuna Transactions product ORB portability layer.
+ // Define an object adapter suitable for use by the JBoss Transactions product ORB portability layer.
RootOA myOA = null;
try
{
- // Initialize the ORB reference using the Arjuna Transactions product ORB portability layer.
+ // Initialize the ORB reference using the JBoss Transactions product ORB portability layer.
myORB = ORB.getInstance("ServerSide");
- // Initialize the object adapter reference using the Arjuna Transactions product ORB portability layer.
+ // Initialize the object adapter reference using the JBoss Transactions product ORB portability layer.
myOA = OA.getRootOA(myORB);
- // Initialize the ORB using the Arjuna Transactions product ORB portability layer.
+ // Initialize the ORB using the JBoss Transactions product ORB portability layer.
myORB.initORB(args, null);
- // Initialize the object adapter reference using the Arjuna Transactions product ORB portability layer.
+ // Initialize the object adapter reference using the JBoss Transactions product ORB portability layer.
myOA.initOA();
}
catch (Exception e)
Modified: labs/jbosstm/trunk/ArjunaJTS/trailmap/src/com/arjuna/demo/jts/txojbank/AccountImpl.java
===================================================================
--- labs/jbosstm/trunk/ArjunaJTS/trailmap/src/com/arjuna/demo/jts/txojbank/AccountImpl.java 2006-09-24 05:52:34 UTC (rev 6395)
+++ labs/jbosstm/trunk/ArjunaJTS/trailmap/src/com/arjuna/demo/jts/txojbank/AccountImpl.java 2006-09-24 07:16:18 UTC (rev 6396)
@@ -37,10 +37,10 @@
import com.arjuna.ats.txoj.LockResult;
/**
- * This account representation is provided as part of the Arjuna Transactions product trailmap. It illustrates the
+ * This account representation is provided as part of the JBoss Transactions product trailmap. It illustrates the
* creation of a Transactional Object 4 Java (TXOJ). As a TXOJ, this class extends LockManager which provides it with
* the standard TXOJ capabilities save_state and restore_state. This allows the object to participate in transactions
- * seamlessly with the Arjuna transaction service.
+ * seamlessly with the JBoss transaction service.
*
* The account provides standard banking operations as with all examples in the trailmap. The source code for these
* operations indicates how the programmer can mediate their access to the state of the object without the need of
Modified: labs/jbosstm/trunk/ArjunaJTS/trailmap/src/com/arjuna/demo/jts/txojbank/BankClient.java
===================================================================
--- labs/jbosstm/trunk/ArjunaJTS/trailmap/src/com/arjuna/demo/jts/txojbank/BankClient.java 2006-09-24 05:52:34 UTC (rev 6395)
+++ labs/jbosstm/trunk/ArjunaJTS/trailmap/src/com/arjuna/demo/jts/txojbank/BankClient.java 2006-09-24 07:16:18 UTC (rev 6396)
@@ -36,7 +36,7 @@
import java.io.IOException;
/**
- * The <CODE>BankClient</CODE> application is an interactive CLI that allows the user of the Arjuna Transactions product
+ * The <CODE>BankClient</CODE> application is an interactive CLI that allows the user of the JBoss Transactions product
* to manipulate a database backed bank under transactional control.
*/
public class BankClient
@@ -447,19 +447,19 @@
*/
public static void main(String[] args)
{
- // Define an ORB suitable for use by the Arjuna Transactions product ORB portability layer.
+ // Define an ORB suitable for use by the JBoss Transactions product ORB portability layer.
ORB myORB = null;
- // Define an object adapter suitable for use by the Arjuna Transactions product ORB portability layer.
+ // Define an object adapter suitable for use by the JBoss Transactions product ORB portability layer.
RootOA myOA = null;
try
{
- // Initialize the ORB reference using the Arjuna Transactions product ORB portability layer.
+ // Initialize the ORB reference using the JBoss Transactions product ORB portability layer.
myORB = ORB.getInstance("ClientSide");
- // Initialize the object adapter reference using the Arjuna Transactions product ORB portability layer.
+ // Initialize the object adapter reference using the JBoss Transactions product ORB portability layer.
myOA = OA.getRootOA(myORB);
- // Initialize the ORB using the Arjuna Transactions product ORB portability layer.
+ // Initialize the ORB using the JBoss Transactions product ORB portability layer.
myORB.initORB(args, null);
- // Initialize the object adapter reference using the Arjuna Transactions product ORB portability layer.
+ // Initialize the object adapter reference using the JBoss Transactions product ORB portability layer.
myOA.initOA();
}
catch (Exception e)
@@ -472,7 +472,7 @@
}
// Obtain a reference to the BankImpl CORBA representation inorder to be able to use it to transactionally
- // invoke banking operations as part of the Arjuna Transactions product trailmap
+ // invoke banking operations as part of the JBoss Transactions product trailmap
// Define the reference to invoke
Bank bank = null;
// Obtain the reference for bank
Modified: labs/jbosstm/trunk/ArjunaJTS/trailmap/src/com/arjuna/demo/jts/txojbank/BankServer.java
===================================================================
--- labs/jbosstm/trunk/ArjunaJTS/trailmap/src/com/arjuna/demo/jts/txojbank/BankServer.java 2006-09-24 05:52:34 UTC (rev 6395)
+++ labs/jbosstm/trunk/ArjunaJTS/trailmap/src/com/arjuna/demo/jts/txojbank/BankServer.java 2006-09-24 07:16:18 UTC (rev 6396)
@@ -55,19 +55,19 @@
public static void main(String[] args)
{
// 0. Define and create the ORB
- // Define an ORB suitable for use by the Arjuna Transactions product ORB portability layer.
+ // Define an ORB suitable for use by the JBoss Transactions product ORB portability layer.
ORB myORB = null;
- // Define an object adapter suitable for use by the Arjuna Transactions product ORB portability layer.
+ // Define an object adapter suitable for use by the JBoss Transactions product ORB portability layer.
RootOA myOA = null;
try
{
- // Initialize the ORB reference using the Arjuna Transactions product ORB portability layer.
+ // Initialize the ORB reference using the JBoss Transactions product ORB portability layer.
myORB = ORB.getInstance("ServerSide");
- // Initialize the object adapter reference using the Arjuna Transactions product ORB portability layer.
+ // Initialize the object adapter reference using the JBoss Transactions product ORB portability layer.
myOA = OA.getRootOA(myORB);
- // Initialize the ORB using the Arjuna Transactions product ORB portability layer.
+ // Initialize the ORB using the JBoss Transactions product ORB portability layer.
myORB.initORB(args, null);
- // Initialize the object adapter reference using the Arjuna Transactions product ORB portability layer.
+ // Initialize the object adapter reference using the JBoss Transactions product ORB portability layer.
myOA.initOA();
}
catch (Exception e)
Modified: labs/jbosstm/trunk/ArjunaJTS/trailmap/src/com/arjuna/demo/recovery/xaresource/TestXAResourceRecovery.java
===================================================================
--- labs/jbosstm/trunk/ArjunaJTS/trailmap/src/com/arjuna/demo/recovery/xaresource/TestXAResourceRecovery.java 2006-09-24 05:52:34 UTC (rev 6395)
+++ labs/jbosstm/trunk/ArjunaJTS/trailmap/src/com/arjuna/demo/recovery/xaresource/TestXAResourceRecovery.java 2006-09-24 07:16:18 UTC (rev 6396)
@@ -43,8 +43,8 @@
import javax.transaction.UserTransaction;
/**
- * The TestXAResourceRecovery class is used to run the Arjuna Transactions product trailmap example which demonstrates
- * the reliability of the Arjuna Transactions product. The test will use some XA resources which crash after returning
+ * The TestXAResourceRecovery class is used to run the JBoss Transactions product trailmap example which demonstrates
+ * the reliability of the JBoss Transactions product. The test will use some XA resources which crash after returning
* PREPARE_OK to the transaction manager, i.e are in the ready to commit phase. Rerunning the test will then see the
* resources recover and be committed.
*/
@@ -100,19 +100,19 @@
}
}
- // Define an ORB suitable for use by the Arjuna Transactions product ORB portability layer.
+ // Define an ORB suitable for use by the JBoss Transactions product ORB portability layer.
ORB myORB = null;
- // Define an object adapter suitable for use by the Arjuna Transactions product ORB portability layer.
+ // Define an object adapter suitable for use by the JBoss Transactions product ORB portability layer.
RootOA myOA = null;
try
{
- // Initialize the ORB reference using the Arjuna Transactions product ORB portability layer.
+ // Initialize the ORB reference using the JBoss Transactions product ORB portability layer.
myORB = ORB.getInstance("test");
- // Initialize the object adapter reference using the Arjuna Transactions product ORB portability layer.
+ // Initialize the object adapter reference using the JBoss Transactions product ORB portability layer.
myOA = OA.getRootOA(myORB);
- // Initialize the ORB using the Arjuna Transactions product ORB portability layer.
+ // Initialize the ORB using the JBoss Transactions product ORB portability layer.
myORB.initORB(args, null);
- // Initialize the object adapter reference using the Arjuna Transactions product ORB portability layer.
+ // Initialize the object adapter reference using the JBoss Transactions product ORB portability layer.
myOA.initOA();
}
catch (Exception e)
Modified: labs/jbosstm/trunk/ArjunaJTS/trailmap/src/com/arjuna/demo/recoverymodule/SimpleRecord.java
===================================================================
--- labs/jbosstm/trunk/ArjunaJTS/trailmap/src/com/arjuna/demo/recoverymodule/SimpleRecord.java 2006-09-24 05:52:34 UTC (rev 6395)
+++ labs/jbosstm/trunk/ArjunaJTS/trailmap/src/com/arjuna/demo/recoverymodule/SimpleRecord.java 2006-09-24 07:16:18 UTC (rev 6396)
@@ -36,10 +36,10 @@
/**
* ACHTUNG!: Implementing an <CODE>AbstractRecord</CODE> is a very advanced feature of the transaction service. It should
- * only be performed by users familiar with the all the concepts used in the Arjuna Transactions product. Please see the
+ * only be performed by users familiar with the all the concepts used in the JBoss Transactions product. Please see the
* ArjunaCore guide for more information about <CODE>AbstractRecord</CODE>s.
*
- * An <CODE>AbstractRecord</CODE> is more generic than an XAResource. In the Arjuna Transactions product an XAResource
+ * An <CODE>AbstractRecord</CODE> is more generic than an XAResource. In the JBoss Transactions product an XAResource
* is wrapped by an <CODE>AbstractRecord</CODE>. Briefly a programmer may wish to implement their own
* <CODE>AbstractRecord</CODE> for any of the following reasons:
* <ol>
Modified: labs/jbosstm/trunk/ArjunaJTS/trailmap/src/com/arjuna/demo/recoverymodule/SimpleRecoveryModule.java
===================================================================
--- labs/jbosstm/trunk/ArjunaJTS/trailmap/src/com/arjuna/demo/recoverymodule/SimpleRecoveryModule.java 2006-09-24 05:52:34 UTC (rev 6395)
+++ labs/jbosstm/trunk/ArjunaJTS/trailmap/src/com/arjuna/demo/recoverymodule/SimpleRecoveryModule.java 2006-09-24 07:16:18 UTC (rev 6396)
@@ -34,7 +34,7 @@
/**
* BEWARE: Implementing a <CODE>RecoveryModule</CODE> is a very advanced feature of the transaction service. It should
- * only be performed by users familiar with the all the concepts used in the Arjuna Transactions product. Please see the
+ * only be performed by users familiar with the all the concepts used in the JBoss Transactions product. Please see the
* ArjunaCore guide for more information about <CODE>AbstractRecord</CODE>s.
*
* This implementation of the recovery module indicates how to write a recovery module to detect if an object is in an
Modified: labs/jbosstm/trunk/ArjunaJTS/trailmap/src/com/arjuna/demo/recoverymodule/TestRecoveryModule.java
===================================================================
--- labs/jbosstm/trunk/ArjunaJTS/trailmap/src/com/arjuna/demo/recoverymodule/TestRecoveryModule.java 2006-09-24 05:52:34 UTC (rev 6395)
+++ labs/jbosstm/trunk/ArjunaJTS/trailmap/src/com/arjuna/demo/recoverymodule/TestRecoveryModule.java 2006-09-24 07:16:18 UTC (rev 6396)
@@ -38,11 +38,11 @@
* Transactions product. Please see the ArjunaCore guide for more information about <CODE>RecoveryModule</CODE>s and
* <CODE>AbstractRecord</CODE>s.
- * This is the entry point into the Arjuna Transactions product advanced trailmap regarding the implementation of a
+ * This is the entry point into the JBoss Transactions product advanced trailmap regarding the implementation of a
* recovery module. It allows a user to create a record within the scope of a transaction and then to commit or
* abort the transaction. The program is quite verbose and describes as it is running what is happening.
*
- * The program illustrates the crash recovery capabilities of the Arjuna Transactions product. The record type it
+ * The program illustrates the crash recovery capabilities of the JBoss Transactions product. The record type it
* defines allows us to crash the application during the commit of the resource. We can then see how the recovery
* manager will (when the application recovers [restarts]) retry to commit the transaction.
*/
@@ -71,7 +71,7 @@
crash = true;
}
- // Create a new Arjuna transaction
+ // Create a new JBoss transaction
AtomicAction tx = new AtomicAction();
// Allocate space to monitor the transaction, this variable is overriden each time the transaction is used.
int actionStatus = tx.begin(); // Top level begin
Modified: labs/jbosstm/trunk/ArjunaJTS/trailmap/src/com/arjuna/demo/simple/HelloClient.java
===================================================================
--- labs/jbosstm/trunk/ArjunaJTS/trailmap/src/com/arjuna/demo/simple/HelloClient.java 2006-09-24 05:52:34 UTC (rev 6395)
+++ labs/jbosstm/trunk/ArjunaJTS/trailmap/src/com/arjuna/demo/simple/HelloClient.java 2006-09-24 07:16:18 UTC (rev 6396)
@@ -38,7 +38,7 @@
import org.omg.CosTransactions.SubtransactionsUnavailable;
/**
- * The <CODE>HelloClient</CODE> is used in the first stage of the Arjuna Transactions product trailmap. It is a trivial
+ * The <CODE>HelloClient</CODE> is used in the first stage of the JBoss Transactions product trailmap. It is a trivial
* JTS client application which invokes a remote method within the scope of a transaction.
*/
public class HelloClient
@@ -52,19 +52,19 @@
public static void main(String[] args)
{
// 0. Define and create the ORB
- // Define an ORB suitable for use by the Arjuna Transactions product ORB portability layer.
+ // Define an ORB suitable for use by the JBoss Transactions product ORB portability layer.
ORB myORB = null;
- // Define an object adapter suitable for use by the Arjuna Transactions product ORB portability layer.
+ // Define an object adapter suitable for use by the JBoss Transactions product ORB portability layer.
RootOA myOA = null;
try
{
- // Initialize the ORB reference using the Arjuna Transactions product ORB portability layer.
+ // Initialize the ORB reference using the JBoss Transactions product ORB portability layer.
myORB = ORB.getInstance("ClientSide");
- // Initialize the object adapter reference using the Arjuna Transactions product ORB portability layer.
+ // Initialize the object adapter reference using the JBoss Transactions product ORB portability layer.
myOA = OA.getRootOA(myORB);
- // Initialize the ORB using the Arjuna Transactions product ORB portability layer.
+ // Initialize the ORB using the JBoss Transactions product ORB portability layer.
myORB.initORB(args, null);
- // Initialize the object adapter reference using the Arjuna Transactions product ORB portability layer.
+ // Initialize the object adapter reference using the JBoss Transactions product ORB portability layer.
myOA.initOA();
}
catch (Exception e)
@@ -77,7 +77,7 @@
}
// 1. Obtain a reference to the HelloImpl CORBA representation inorder to be able to use it to transactionally
- // invoke a method to validate the installation of the Arjuna Transactions product
+ // invoke a method to validate the installation of the JBoss Transactions product
// Define the reference to invoke
Hello hello = null;
// Obtain the reference for hello
Modified: labs/jbosstm/trunk/ArjunaJTS/trailmap/src/com/arjuna/demo/simple/HelloServer.java
===================================================================
--- labs/jbosstm/trunk/ArjunaJTS/trailmap/src/com/arjuna/demo/simple/HelloServer.java 2006-09-24 05:52:34 UTC (rev 6395)
+++ labs/jbosstm/trunk/ArjunaJTS/trailmap/src/com/arjuna/demo/simple/HelloServer.java 2006-09-24 07:16:18 UTC (rev 6396)
@@ -47,19 +47,19 @@
public static void main(String[] args)
{
// 0. Define and create the ORB
- // Define an ORB suitable for use by the Arjuna Transactions product ORB portability layer.
+ // Define an ORB suitable for use by the JBoss Transactions product ORB portability layer.
ORB myORB = null;
- // Define an object adapter suitable for use by the Arjuna Transactions product ORB portability layer.
+ // Define an object adapter suitable for use by the JBoss Transactions product ORB portability layer.
RootOA myOA = null;
try
{
- // Initialize the ORB reference using the Arjuna Transactions product ORB portability layer.
+ // Initialize the ORB reference using the JBoss Transactions product ORB portability layer.
myORB = ORB.getInstance("ServerSide");
- // Initialize the object adapter reference using the Arjuna Transactions product ORB portability layer.
+ // Initialize the object adapter reference using the JBoss Transactions product ORB portability layer.
myOA = OA.getRootOA(myORB);
- // Initialize the ORB using the Arjuna Transactions product ORB portability layer.
+ // Initialize the ORB using the JBoss Transactions product ORB portability layer.
myORB.initORB(args, null);
- // Initialize the object adapter reference using the Arjuna Transactions product ORB portability layer.
+ // Initialize the object adapter reference using the JBoss Transactions product ORB portability layer.
myOA.initOA();
}
catch (Exception e)
Modified: labs/jbosstm/trunk/atsintegration/docbuild/docs/rmi-iiop.xml
===================================================================
--- labs/jbosstm/trunk/atsintegration/docbuild/docs/rmi-iiop.xml 2006-09-24 05:52:34 UTC (rev 6395)
+++ labs/jbosstm/trunk/atsintegration/docbuild/docs/rmi-iiop.xml 2006-09-24 07:16:18 UTC (rev 6396)
@@ -218,14 +218,14 @@
<FONT FACE="Courier, monospace" SIZE="2">
jboss.home
</FONT>
- The home directory of the JBoss server with Arjuna+JBoss
+ The home directory of the JBoss server with Arjuna and JBoss
installed (e.g. /opt/jboss-3.2.2/)</P>
<P>
<FONT FACE="Courier, monospace">
- <FONT SIZE="2">arjunats.home</FONT>
+ <FONT SIZE="2">jbossts.home</FONT>
</FONT>
- The home directory of the Arjuna Transaction Service
- installation (e.g. /opt/arjuna/arjunajboss-1.0/ats-3.1/)</P>
+ The home directory of the JBoss Transaction Service
+ installation (e.g. /opt/jbossts/)</P>
<P>
<FONT SIZE="2">
<FONT FACE="Courier, monospace">
Modified: labs/jbosstm/trunk/atsintegration/scripts/run-tools.bat
===================================================================
--- labs/jbosstm/trunk/atsintegration/scripts/run-tools.bat 2006-09-24 05:52:34 UTC (rev 6395)
+++ labs/jbosstm/trunk/atsintegration/scripts/run-tools.bat 2006-09-24 07:16:18 UTC (rev 6396)
@@ -23,7 +23,7 @@
if "%@HOME_DIRECTORY@%"=="" goto atserror
if "%JBOSS_HOME%"=="" goto jbosserror
-rem Setup the environment for the Arjuna Transaction Service
+rem Setup the environment for the JBoss Transaction Service
call "%@HOME_DIRECTORY@%\bin\setup-env.bat"
rem Setup the required JBoss classpath
Modified: labs/jbosstm/trunk/atsintegration/scripts/run-tools.sh
===================================================================
--- labs/jbosstm/trunk/atsintegration/scripts/run-tools.sh 2006-09-24 05:52:34 UTC (rev 6395)
+++ labs/jbosstm/trunk/atsintegration/scripts/run-tools.sh 2006-09-24 07:16:18 UTC (rev 6396)
@@ -46,7 +46,7 @@
;;
esac
-# Setup the environment for the Arjuna Transaction Service
+# Setup the environment for the JBoss Transaction Service
. "$@HOME_DIRECTORY@/bin/setup-env.sh"
# Setup the required JBOSS classpath
Modified: labs/jbosstm/trunk/common/classes/com/arjuna/common/internal/util/logging/commonPropertyManager.java
===================================================================
--- labs/jbosstm/trunk/common/classes/com/arjuna/common/internal/util/logging/commonPropertyManager.java 2006-09-24 05:52:34 UTC (rev 6395)
+++ labs/jbosstm/trunk/common/classes/com/arjuna/common/internal/util/logging/commonPropertyManager.java 2006-09-24 07:16:18 UTC (rev 6396)
@@ -25,7 +25,7 @@
*
* The properties can originate either from a configuration file (by default CommonLogging.properties or
* CommonLogging.xml) or it can be primed by using the class directly from an embedding product (such as
- * the Arjuna Transaction Service).
+ * the JBoss Transaction Service).
*
* The default file location can be overridden by setting the property
* "com.arjuna.common.util.logging.propertiesFile"
Modified: labs/jbosstm/trunk/ext/third_party_licenses.txt
===================================================================
--- labs/jbosstm/trunk/ext/third_party_licenses.txt 2006-09-24 05:52:34 UTC (rev 6395)
+++ labs/jbosstm/trunk/ext/third_party_licenses.txt 2006-09-24 07:16:18 UTC (rev 6396)
@@ -1,4 +1,4 @@
-TERMS AND CONDITIONS FOR THIRD PARTY PRODUCTS THAT MAY ACCOMPANY ARJUNATS
+TERMS AND CONDITIONS FOR THIRD PARTY PRODUCTS THAT MAY ACCOMPANY JBOSSTS
THE TERMS AND CONDITIONS APPEARING BELOW APPLY ONLY TO THAT PORTION OF THE SOFTWARE THAT IS THE
PARTICULAR THIRD PARTY PRODUCT AND DO NOT OVERRIDE ANY ARJUNA SOFTWARE OR ANY OTHER PRODUCTS TERMS
ASSOCIATED WITH OTHER ELEMENTS OF THE SOFTWARE.
More information about the jboss-svn-commits
mailing list