[jboss-svn-commits] JBL Code SVN: r21932 - in labs/jbosstm/trunk: ArjunaJTS and 5 other directories.
jboss-svn-commits at lists.jboss.org
jboss-svn-commits at lists.jboss.org
Wed Aug 27 09:23:50 EDT 2008
Author: adinn
Date: 2008-08-27 09:23:50 -0400 (Wed, 27 Aug 2008)
New Revision: 21932
Modified:
labs/jbosstm/trunk/ArjunaJTA/INSTALL
labs/jbosstm/trunk/ArjunaJTS/INSTALL
labs/jbosstm/trunk/XTS/demo/BUILDING
labs/jbosstm/trunk/XTS/demo/README
labs/jbosstm/trunk/XTS/demo/docs/about.xml
labs/jbosstm/trunk/XTS/demo/docs/atomictransaction.xml
labs/jbosstm/trunk/XTS/demo/docs/businessactivity.xml
labs/jbosstm/trunk/XTS/demo/docs/deploying.xml
labs/jbosstm/trunk/XTS/demo/docs/includes/trailmap_navigation.xml
labs/jbosstm/trunk/XTS/demo/docs/index.xml
labs/jbosstm/trunk/XTS/demo/docs/installcontent.xml
labs/jbosstm/trunk/XTS/demo/docs/sourcecode.xml
labs/jbosstm/trunk/XTS/demo/docs/styles.css
labs/jbosstm/trunk/XTS/demo/docs/wherenext.xml
labs/jbosstm/trunk/XTS/demo/xsl/ATL_LookAndFeel.xsl
labs/jbosstm/trunk/XTS/docs/XTSRecoveryNotes.txt
Log:
mods to XTS documentation for 4.4 release - fixes JBTM-358
Modified: labs/jbosstm/trunk/ArjunaJTA/INSTALL
===================================================================
--- labs/jbosstm/trunk/ArjunaJTA/INSTALL 2008-08-27 12:48:59 UTC (rev 21931)
+++ labs/jbosstm/trunk/ArjunaJTA/INSTALL 2008-08-27 13:23:50 UTC (rev 21932)
@@ -54,10 +54,11 @@
The default XTS build produces a service archive which contains both
sets of partipant and coordinator services configured to support
-transactional web service invocations within a single JVM bound to
-address localhost and port 8080. This default build is suitable for
-demonstrating the functionality of XTS using the supplied demo
-programs. One of the demos displays use of the WS 1.1 protocols when
+transactional web service invocations within a single JVM. The services
+employ the JBoss Application Server bind address and JBoss Web listener
+port which default to address localhost and port 8080. This default build
+is suitable for demonstrating the functionality of XTS using the supplied
+demo programs. One of the demos displays use of the WS 1.1 protocols when
invoking web services via JaxWS. The other displays use of the WS 1.0
protcols when invoking web services via JaxRPC.
@@ -90,50 +91,72 @@
This will install the sar in subdirectory server/default/deploy of
$JBOSS_HOME
-Command line options can be used
+Stand-alone coordinator configuration
+---------------------------------
- i) to build a service archive for use with a different application
- server bind address/port
+The JBoss AS command line can be used to disable use of the local
+coordinator services and direct the participants to negotiate with
+a remote coordinator located in a different JBoss application server.
-or
+The -D option can be used to set a property defining an absolute URL
+for the coordinator service to be used by XTS clients. So, for example,
+the 1.0 and 1.1 implementations would be configured independently by
+providing, respectively, the following command line arguments
- ii) to disable use of the local coordinator services and direct the
- participants to negotiate with a remote coordinator located in a
- different JBoss application server
+ -Dorg.jboss.jbossts.xts.coordinatorURL=http://foo.example.com:8080/ws-c10/soap/ActivationCoordinator
-So, for example,
+ -Dorg.jboss.jbossts.xts11.coordinatorURL=http://bar.example.com:9090/ws-c11/ActivationService
- setenv JBOSS_HOME <JBossDir>
- cd <JBossTSDir>/XTS/sar
- ant clean install
- cd sar
- ant deploy -Dhostname=foo.example.com -Dport=9090
+This would cause all XTS 1.0 clients to negotiate with the coordinator
+services deployed on host foo.example.com via port 8080 and all XTS 1.1
+clients to negotiate with the coordinator services deployed on host
+bar.example.com via port 9090. The URL paths supplied are appropriate
+to a JBoss AS with XTS deployed. These will need to be redefined if
+another vendor's coordination service implementation is being used.
-will build and deploy a sar suitable for an application server bound
-to address foo.example.com using web server port 9090.
+It is also possible to respecify individual components of the coordinator
+URL using the following property settings
-Having deployed this service it would then be possible to use it as a
-remote coordinator for a second JBoss application server bound to
-address bar.example.com and using web server port 8080. The sar for
-the second server could be built and deployed as follows:
+ org.jboss.jbossts.xts.coordinator.host
+ org.jboss.jbossts.xts.coordinator.port
+ org.jboss.jbossts.xts.coordinator.path
+ org.jboss.jbossts.xts11.coordinator.host
+ org.jboss.jbossts.xts11.coordinator.port
+ org.jboss.jbossts.xts11.coordinator.path
+
+The host and port default to the server bind address and the JBoss Web
+listener port. The paths default to the values supplied in the example
+above.
+
+It is possible to rebuild the XTS sar so that it employs a stand-alone
+coordinator without the need to supply arguments on the AS command line.
+
+So, for example,
+
setenv JBOSS_HOME <JBossDir>
cd <JBossTSDir>/XTS/sar
ant clean install
cd sar
- ant deploy -Dhostname=bar.example.com -Dport=8080 \
- -Dcoordinator.hostname=foo.example.com \
+ ant deploy -Dcoordinator.hostname=foo.example.com \
-Dcoordinator.port=9090
+will build and deploy a sar which, by default will direct clients
+to the coordinator located in a JBoss AS instance running on host
+foo.example.com and configured to use port 9090 as the JBoss Web
+listener port. It is not possible to redefine the coordinator URL
+path using this mechanism.
+
Configuration of a remote coordinator provided by another XTS
implementation is available by editing the configuration files in
-directory XTS/xts-install/conf and setting an appropriate URl for the
-coordinator URL property. The value specified for property
-com.arjuna.mw.wst.coordinatorURL in file wstx.xml is used by the 1.0
-protocol implementation. The value specified for property
-com.arjuna.mw.wst11.coordinatorURL in file wstx11.xml is used by the
-1.1 protocol implementation.
+directory XTS/xts-install/conf and setting an appropriate URL for
+the coordinator URL property. The value specified for property
+org.jboss.jbossts.xts.coordinatorURL in file wstx.xml is used by
+the 1.0 protocol implementation. The value specified for property
+org.jboss.jbossts.xts11.coordinatorURL in file wstx11.xml is used
+by the 1.1 protocol implementation.
+
Warning:
-------
Modified: labs/jbosstm/trunk/ArjunaJTS/INSTALL
===================================================================
--- labs/jbosstm/trunk/ArjunaJTS/INSTALL 2008-08-27 12:48:59 UTC (rev 21931)
+++ labs/jbosstm/trunk/ArjunaJTS/INSTALL 2008-08-27 13:23:50 UTC (rev 21932)
@@ -132,10 +132,11 @@
The default XTS build produces a service archive which contains both
sets of partipant and coordinator services configured to support
-transactional web service invocations within a single JVM bound to
-address localhost and port 8080. This default build is suitable for
-demonstrating the functionality of XTS using the supplied demo
-programs. One of the demos displays use of the WS 1.1 protocols when
+transactional web service invocations within a single JVM. The services
+employ the JBoss Application Server bind address and JBoss Web listener
+port which default to address localhost and port 8080. This default build
+is suitable for demonstrating the functionality of XTS using the supplied
+demo programs. One of the demos displays use of the WS 1.1 protocols when
invoking web services via JaxWS. The other displays use of the WS 1.0
protcols when invoking web services via JaxRPC.
@@ -168,49 +169,70 @@
This will install the sar in subdirectory server/default/deploy of
$JBOSS_HOME
-Command line options can be used
+Stand-alone coordinator configuration
+---------------------------------
- i) to build a service archive for use with a different application
- server bind address/port
+The JBoss AS command line can be used to disable use of the local
+coordinator services and direct the participants to negotiate with
+a remote coordinator located in a different JBoss application server.
-or
+The -D option can be used to set a property defining an absolute URL
+for the coordinator service to be used by XTS clients. So, for example,
+the 1.0 and 1.1 implementations would be configured independently by
+providing, respectively, the following command line arguments
- ii) to disable use of the local coordinator services and direct the
- participants to negotiate with a remote coordinator located in a
- different JBoss application server
+ -Dorg.jboss.jbossts.xts.coordinatorURL=http://foo.example.com:8080/ws-c10/soap/ActivationCoordinator
-So, for example,
+ -Dorg.jboss.jbossts.xts11.coordinatorURL=http://bar.example.com:9090/ws-c11/ActivationService
- setenv JBOSS_HOME <JBossDir>
- cd <JBossTSDir>/XTS/sar
- ant clean install
- cd sar
- ant deploy -Dhostname=foo.example.com -Dport=9090
+This would cause all XTS 1.0 clients to negotiate with the coordinator
+services deployed on host foo.example.com via port 8080 and all XTS 1.1
+clients to negotiate with the coordinator services deployed on host
+bar.example.com via port 9090. The URL paths supplied are appropriate
+to a JBoss AS with XTS deployed. These will need to be redefined if
+another vendor's coordination service implementation is being used.
-will build and deploy a sar suitable for an application server bound
-to address foo.example.com using web server port 9090.
+It is also possible to respecify individual components of the coordinator
+URL using the following property settings
-Having deployed this service it would then be possible to use it as a
-remote coordinator for a second JBoss application server bound to
-address bar.example.com and using web server port 8080. The sar for
-the second server could be built and deployed as follows:
+ org.jboss.jbossts.xts.coordinator.host
+ org.jboss.jbossts.xts.coordinator.port
+ org.jboss.jbossts.xts.coordinator.path
+ org.jboss.jbossts.xts11.coordinator.host
+ org.jboss.jbossts.xts11.coordinator.port
+ org.jboss.jbossts.xts11.coordinator.path
+
+The host and port default to the server bind address and the JBoss Web
+listener port. The paths default to the values supplied in the example
+above.
+
+It is possible to rebuild the XTS sar so that it employs a stand-alone
+coordinator without the need to supply arguments on the AS command line.
+
+So, for example,
+
setenv JBOSS_HOME <JBossDir>
cd <JBossTSDir>/XTS/sar
ant clean install
cd sar
- ant deploy -Dhostname=bar.example.com -Dport=8080 \
- -Dcoordinator.hostname=foo.example.com \
+ ant deploy -Dcoordinator.hostname=foo.example.com \
-Dcoordinator.port=9090
+will build and deploy a sar which, by default will direct clients
+to the coordinator located in a JBoss AS instance running on host
+foo.example.com and configured to use port 9090 as the JBoss Web
+listener port. It is not possible to redefine the coordinator URL
+path using this mechanism.
+
Configuration of a remote coordinator provided by another XTS
implementation is available by editing the configuration files in
-directory XTS/xts-install/conf and setting an appropriate URl for the
-coordinator URL property. The value specified for property
-com.arjuna.mw.wst.coordinatorURL in file wstx.xml is used by the 1.0
-protocol implementation. The value specified for property
-com.arjuna.mw.wst11.coordinatorURL in file wstx11.xml is used by the
-1.1 protocol implementation.
+directory XTS/xts-install/conf and setting an appropriate URL for
+the coordinator URL property. The value specified for property
+org.jboss.jbossts.xts.coordinatorURL in file wstx.xml is used by
+the 1.0 protocol implementation. The value specified for property
+org.jboss.jbossts.xts11.coordinatorURL in file wstx11.xml is used
+by the 1.1 protocol implementation.
Warning:
-------
Modified: labs/jbosstm/trunk/XTS/demo/BUILDING
===================================================================
--- labs/jbosstm/trunk/XTS/demo/BUILDING 2008-08-27 12:48:59 UTC (rev 21931)
+++ labs/jbosstm/trunk/XTS/demo/BUILDING 2008-08-27 13:23:50 UTC (rev 21932)
@@ -18,33 +18,25 @@
# @author JBoss Inc.
#
-This demo has been written for, and tested on, JBoss4.2.2.GA and
-JBoss5.0Beta4. Please download and install one of these app servers
-from the JBoss website.
+This demo has been written for, and tested on, JBoss5.0.CR1.
+Please download and install one of these app servers from the
+JBoss website.
Follow these steps to build the demo for JBoss
- edit jboss.properties and replace variables as directed in the comments
- add java and ant to your path
- set environment variable JBOSS_HOME to point to the root directory of an
- instance of JBoss4.2 or JBoss5.0Beta4
- - for JBoss5.0Beta4 execute 'sh build.sh jboss clean deploy' on unix or
+ instance of JBoss5.0.0.CR1
+ - execute 'sh build.sh jboss clean deploy' on unix or
'build.bat jboss clean deploy' on windows
- - for JBoss4.2 execute 'sh build.sh jboss clean sa-deploy' on unix or
- 'build.bat jboss clean sa-deploy' on windows
Open a browser and enter the xts-demo url (e.g. http://localhost:8080/xts-demo)
An alternative version of the demo can be built using JaxRPC instead
-of JaxWS. For JBoss5.0.Beta4 this can be built by supplying the
-argument 'deployrpc' in place of 'deploy' on the 'execute' command
-line detailed above. For JBoss4.2 it can be built by supplying the
-argument 'sa-deployrpc' in place of 'sa-deploy'. Access the demo using
-the same url.
+of JaxWS by supplying the argument 'deployrpc' in place of 'deploy' on
+the 'execute' command line detailed above.
-n.b. deployment of the demo to JbossAS 5.0Beta4 assumes that the XTS
+n.b. deployment of the demo to JbossAS 5.0.CR1 assumes that the XTS
has already been deployed as a service archive (sar). See the INSTALL
-file in your ArjunaJTS install tree for instructions on how to perform
-this deployment. XTS sar deployment currently requires the web
-listener hostname and port to be "localhost" and "8080". This
-restriction will be lifted in future releases. Use of a stand alone
-coordinator is also not currently supported in JbossAS 5.0Beta4.
+file in your ArjunaJTA or ArjunaJTS install tree for instructions on how
+to perform this deployment.
Modified: labs/jbosstm/trunk/XTS/demo/README
===================================================================
--- labs/jbosstm/trunk/XTS/demo/README 2008-08-27 12:48:59 UTC (rev 21931)
+++ labs/jbosstm/trunk/XTS/demo/README 2008-08-27 13:23:50 UTC (rev 21932)
@@ -1,8 +1,9 @@
This is the raw demo source directory for the XTS demo program
-(XTS/demo). Do not attempt to build the demo from this directory a sit
+(XTS/demo). Do not attempt to build the demo from this directory as it
will not work.
-Run the command 'ant clean install' in the parent directory (XTS) to
+Run the command 'ant clean install' in the parent directory (XTS).
+This will:
- create the xts install directory (XTS/xts-install)
Modified: labs/jbosstm/trunk/XTS/demo/docs/about.xml
===================================================================
--- labs/jbosstm/trunk/XTS/demo/docs/about.xml 2008-08-27 12:48:59 UTC (rev 21931)
+++ labs/jbosstm/trunk/XTS/demo/docs/about.xml 2008-08-27 13:23:50 UTC (rev 21932)
@@ -16,7 +16,7 @@
MA 02110-1301, USA.
- (C) 2005-2006,
+ (C) 2005-2008,
@author JBoss Inc.
-->
<page title="XML Transaction Service Demonstration Application: About the sample application" rootpath="../..">
@@ -37,7 +37,7 @@
<html>
<p>
The sample application features some simple transactional Web services, a client application, deployment metadata files and a build script.
- The application is designed to introduce some of the key features of the XML Transaction component of JBossTS 4.3.0 and help you get started with writing your own transactional Web services applications.
+ The application is designed to introduce some of the key features of the XML Transaction component of JBossTS 4.4.0 and help you get started with writing your own transactional Web services applications.
</p>
<p>
The application is based around a simple booking scenario. The services provide the ability to transactionally reserve resources,
@@ -52,8 +52,8 @@
The client side of the application is a servlet which allows the user to select the required reservations and then books a night out by making invocations on each of the services within the scope of a Web Services transaction.
</p>
<p>
- The demo is implemented in two versions. The standard version exposes the services as JaxWS service endpoints. The client obtains service endpoint proxies from JaxWS and uses them to invoke the remote service methods.
- The alternative implementation demonstrates how to invoke legacy services. It uses JaxRPC to invoke the remote methods of services exposed as classes implementing the Remote interface.
+ The demo is implemented in two versions. The standard version exposes the services as JaxWS service endpoints. The client obtains service endpoint proxies from JaxWS and uses them to invoke the remote service methods. This version of the demo employs the XTS 1.1 protocol implementation.
+ The alternative implementation demonstrates how to invoke legacy services. It uses JaxRPC to invoke the remote methods of services exposed as classes implementing the Remote interface. This version of the demo employs the XTS 1.0 protocol implementation.
</p>
<p>
Full source code for the services and the client is included, along with an ant script for building and deploying the code.
Modified: labs/jbosstm/trunk/XTS/demo/docs/atomictransaction.xml
===================================================================
--- labs/jbosstm/trunk/XTS/demo/docs/atomictransaction.xml 2008-08-27 12:48:59 UTC (rev 21931)
+++ labs/jbosstm/trunk/XTS/demo/docs/atomictransaction.xml 2008-08-27 13:23:50 UTC (rev 21932)
@@ -16,7 +16,7 @@
MA 02110-1301, USA.
- (C) 2005-2006,
+ (C) 2005-2008,
@author JBoss Inc.
-->
<page title="XML Transaction Service Demonstration Application: Atomic Transactions" rootpath="../..">
Modified: labs/jbosstm/trunk/XTS/demo/docs/businessactivity.xml
===================================================================
--- labs/jbosstm/trunk/XTS/demo/docs/businessactivity.xml 2008-08-27 12:48:59 UTC (rev 21931)
+++ labs/jbosstm/trunk/XTS/demo/docs/businessactivity.xml 2008-08-27 13:23:50 UTC (rev 21932)
@@ -16,7 +16,7 @@
MA 02110-1301, USA.
- (C) 2005-2006,
+ (C) 2005-2008,
@author JBoss Inc.
-->
<page title="XML Transaction Service Demonstration Application: Business Activities" rootpath="../..">
Modified: labs/jbosstm/trunk/XTS/demo/docs/deploying.xml
===================================================================
--- labs/jbosstm/trunk/XTS/demo/docs/deploying.xml 2008-08-27 12:48:59 UTC (rev 21931)
+++ labs/jbosstm/trunk/XTS/demo/docs/deploying.xml 2008-08-27 13:23:50 UTC (rev 21932)
@@ -16,7 +16,7 @@
MA 02110-1301, USA.
- (C) 2005-2006,
+ (C) 2005-2008,
@author JBoss Inc.
-->
<page title="XML Transaction Service Demonstration Application: Deploying the sample application" rootpath="../..">
@@ -42,45 +42,30 @@
To proceed, you will need to install ant (<a class="linkscoloured" href="http://ant.apache.org/" target="_blank">http://ant.apache.org/</a>) to take advantage of the supplied build file. Version 1.6.1 or later of ant is recommended for this application. The application may not function correctly with versions prior to 1.5.
</p>
<p>
- This release has been tested against JBoss 4.2.2.GA and JBoss 5.0.Beta4.
+ This release has been tested against JBoss 5.0.0.CR1.
</p>
- <p>
- Deploying into JBoss 4.2.
- </p>
- <ol>
- <li><p>Install JBoss 4.2.</p>
- </li>
- <li><p>Edit the <code><xts-home>/demo/jboss.properties</code> file, replacing the <code>JBOSS_HOSTNAME</code> and <code>JBOSS_PORT</code> with the values used by your JBoss server web listener. Replace <code>JBOSS_URLSTUB</code> with a path used as the location for the demo application web services</p></li>
- <li><p>Set environment variable <code>JBOSS_HOME</code> to point to the root directory of your JBoss installation.</p></li>
- <li><p>Compile the application source, build the application archive file and deploy it into JBoss deploy directory by typing '<code>build.sh jboss clean sa-deploy</code>' on Unix or '<code>build.bat jboss clean sa-deploy</code>' on Windows</p></li>
- <li><p>Run the application server by using the run.sh or run.bat command.</p></li>
- <li><p>Invoke the demo client by browsing the URL (e.g.): <code>http://hostname:port/xts-demo/</code></p></li>
- </ol>
- <p>
- n.b. the JaxRPC based version of the demo can be built and deployed by substituting target '<code>sa-deploy</code>' in the commands listed above with the alternative target '<code>sa-deployrpc</code>'
- </p>
- <p>
- This release of the demo application includes the ability to run the client against a mixture of backend webservices. The property files contain the URLs of the webservices, which can be changed to exercise any combination and demonstrate a distributed transaction.
- The services are started using the same mechanism as above. Each platform will be running its own copy of the webservices but the deployed client will access those services configured in the relevant property file.
- </p>
<p>
- Deploying into JBoss 5.0.Beta4.
+ Deploying into JBoss 5.0.0.CR1.
</p>
- <p>
- Note that at present JBoss JTS and XTS must be manually deployed into JBoss 5.0. In full 5.0 releases the XTS component should be bundled into the release as a service archive.
- </p>
<ol>
<li><p>Install JBoss 5.0.</p>
</li>
- <li><p>Build and deploy JBoss JTS and JBoss XTS service archive (execute '<code>ant jbossjts</code>' in the JBossTS source tree and follow the deployment instructions in file INSTALL of the resulting JBossTS install tree).</p>
+ <li><p>Set environment variable <code>JBOSS_HOME</code> to point to the root directory of your JBoss installation.</p></li>
+ <li><p>(Optional**) Build and deploy JBoss JTA or JBoss JTS (execute '<code>ant jbossjta</code>' or '<code>ant jbossjts</code>' in the JBossTS source tree and follow the deployment instructions in file INSTALL of the resulting JBossTS install tree).</p>
</li>
- <li><p>Edit the <code><xts-home>/demo/jboss.properties</code> file, replacing the <code>JBOSS_HOSTNAME</code> and <code>JBOSS_PORT</code> with the values used by your JBoss server web listener. Replace <code>JBOSS_URLSTUB</code> with a path used as the location for the demo application web services. (n.b. at present the hostname and port must be supplied as <code>localhost</code> and <code>8080</code></p></li>
- <li><p>Set environment variable <code>JBOSS_HOME</code> to point to the root directory of your JBoss installation.</p></li>
- <li><p>Compile the application source, build the application archive file and deploy it into JBoss deploy directory by typing '<code>build.sh jboss clean deploy</code>' on Unix or '<code>build.bat jboss clean deploy</code>' on Windows</p></li>
+ <li><p>(Optional**) Build JBoss XTS (follow the XTS build instructions in file INSTALL of the JBossTS install tree).</p>
+ </li>
+ <li><p>Deploy the XTS service archive <code><jbossts 4.4.0 xts>/xts-install/sar/jbossxts.sar</code> into the JBoss 5.0 server deploy directory. n.b. due to a bug in the JBossWS implementation it is only possible to deploy the XTS service archive after starting JBoss AS.</p>
+ </li>
+ <li><p>Edit the <code><jbossts 4.4.0 xts>/xts-install/demo/jboss.properties</code> file, replacing the <code>JBOSS_HOSTNAME</code> and <code>JBOSS_PORT</code> with the bind address and port used by your JBoss server and Jboss Web listener. Replace <code>JBOSS_URLSTUB</code> with a path used as the location for the demo application web services.</p></li>
+ <li><p>Compile the application source under <code><jbossts 4.4.0 xts>/xts-install/demo</code>, build the application archive file and deploy it into JBoss deploy directory by typing '<code>build.sh jboss clean deploy</code>' on Unix or '<code>build.bat jboss clean deploy</code>' on Windows</p></li>
<li><p>Run the application server by using the run.sh or run.bat command.</p></li>
<li><p>Invoke the demo client by browsing the URL (e.g.): <code>http://hostname:port/xts-demo/</code></p></li>
</ol>
<p>
+ ** the JBoss 5.0 installation may include a pre-built, pre-installed JBossTS build and a pre-built XTS service archive.
+ </p>
+ <p>
n.b. the JaxRPC based version of the demo can be built and deployed by substituting target '<code>deploy</code>' in the commands listed above with the alternative target '<code>deployrpc</code>'
</p>
<p>Using the application</p>
Modified: labs/jbosstm/trunk/XTS/demo/docs/includes/trailmap_navigation.xml
===================================================================
--- labs/jbosstm/trunk/XTS/demo/docs/includes/trailmap_navigation.xml 2008-08-27 12:48:59 UTC (rev 21931)
+++ labs/jbosstm/trunk/XTS/demo/docs/includes/trailmap_navigation.xml 2008-08-27 13:23:50 UTC (rev 21932)
@@ -16,7 +16,7 @@
MA 02110-1301, USA.
- (C) 2005-2006,
+ (C) 2005-2008,
@author JBoss Inc.
-->
Modified: labs/jbosstm/trunk/XTS/demo/docs/index.xml
===================================================================
--- labs/jbosstm/trunk/XTS/demo/docs/index.xml 2008-08-27 12:48:59 UTC (rev 21931)
+++ labs/jbosstm/trunk/XTS/demo/docs/index.xml 2008-08-27 13:23:50 UTC (rev 21932)
@@ -16,7 +16,7 @@
MA 02110-1301, USA.
- (C) 2005-2006,
+ (C) 2005-2008,
@author JBoss Inc.
-->
<page title="XML Transaction Service Demonstration Application: Introduction" rootpath="../..">
@@ -34,7 +34,7 @@
<area title="Introduction">
<html>
<p>
- Welcome to the "Night Out" sample application for the XML Transaction component of JBossTS 4.3.0.
+ Welcome to the "Night Out" sample application for the XML Transaction component of JBossTS 4.4.0.
</p>
<p>
This documentation will help you get started with using the JBossTS Web services transactioning product.
Modified: labs/jbosstm/trunk/XTS/demo/docs/installcontent.xml
===================================================================
--- labs/jbosstm/trunk/XTS/demo/docs/installcontent.xml 2008-08-27 12:48:59 UTC (rev 21931)
+++ labs/jbosstm/trunk/XTS/demo/docs/installcontent.xml 2008-08-27 13:23:50 UTC (rev 21932)
@@ -16,7 +16,7 @@
MA 02110-1301, USA.
- (C) 2005-2006,
+ (C) 2005-2008,
@author JBoss Inc.
-->
<page title="XML Transaction Service Demonstration Application: Installation Content" rootpath="../..">
@@ -35,22 +35,22 @@
<area title="Installation Content">
<html>
<p>
- The installer should have installed the following directories under <jbosst 4.3.0 install>/wst directory:
+ The installer should have installed the following directories under directory <jbossts 4.4.0 xts>/xts-install:
<ul>
<p>conf: product configuration files.</p>
- <p>coordinator: an application independent version of the transaction coordinator.</p>
<p>demo: a sample application and introductory documentation.</p>
<p>docs: product manuals and API javadocs.</p>
<p>lib: jar files for the JBossTS components and their 3rd party prerequisites.</p>
+ <p>sar: deployable JBoss service archive containing the XTS 1.0 and 1.1 implementation.</p>
<p>webapps: pre built J2EE web applications for the product components.</p>
</ul>
</p>
<p>
In addition, you will require a Web services platform on which to deploy and run the product.
- This release of the XML Transaction component of JBossTS 4.3.0 is designed to run within JBoss.
+ This release of the XML Transaction component of JBossTS 4.4.0 is designed to run within JBoss.
</p>
<p>
- This release has been tested on JBoss 4.2.2.GA and JBoss 5.0.Beta4.
+ This release has been tested on JBoss 5.0.0.CR1.
</p>
<p>
To compile, deploy and run the sample application we also recommend using java SDK 1.5 and Apache ant 1.6.1 or later.
Modified: labs/jbosstm/trunk/XTS/demo/docs/sourcecode.xml
===================================================================
--- labs/jbosstm/trunk/XTS/demo/docs/sourcecode.xml 2008-08-27 12:48:59 UTC (rev 21931)
+++ labs/jbosstm/trunk/XTS/demo/docs/sourcecode.xml 2008-08-27 13:23:50 UTC (rev 21932)
@@ -16,7 +16,7 @@
MA 02110-1301, USA.
- (C) 2005-2006,
+ (C) 2005-2008,
@author JBoss Inc.
-->
<page title="XML Transaction Service Demonstration Application: Source code overview" rootpath="../..">
@@ -36,9 +36,9 @@
<area title="Source code overview">
<html>
<p>
- You can begin experimenting with the XML Transaction component of JBoss 4.3.0 by editing the sample application source code, which is heavily commented to assist your understanding.
- The source code can be found in the <jbossts 4.3.0 install>demo/src directory. Deployment descriptors for the application can be found iin directory <jbossts 4.3.0 install>demo/dd.
- (corresponding files for the JaxRPC implementation are in directories <jbossts 4.3.0 install>demo/srcrpc and <jbossts 4.3.0 install>demo/ddrpc).
+ You can begin experimenting with the XML Transaction component of JBoss 4.4.0 by editing the sample application source code, which is heavily commented to assist your understanding.
+ The source code can be found in the <jbossts 4.4.0 xts>/xts-install/demo/src directory. Deployment descriptors for the application can be found iin directory <jbossts 4.4.0 xtsl>/xts-install/demo/dd.
+ (corresponding files for the JaxRPC implementation are in directories <jbossts 4.4.0 xts>/xts-install/demo/srcrpc and <jbossts 4.4.0 xts>/xts-install/demo/ddrpc).
</p>
<p>
It is structured as follows:
Modified: labs/jbosstm/trunk/XTS/demo/docs/styles.css
===================================================================
--- labs/jbosstm/trunk/XTS/demo/docs/styles.css 2008-08-27 12:48:59 UTC (rev 21931)
+++ labs/jbosstm/trunk/XTS/demo/docs/styles.css 2008-08-27 13:23:50 UTC (rev 21932)
@@ -15,7 +15,7 @@
* Foundation, Inc., 51 Franklin Street, Fifth Floor, Boston,
* MA 02110-1301, USA.
*
- * (C) 2005-2006,
+ * (C) 2005-2008,
* @author JBoss Inc.
*/
A:hover {
Modified: labs/jbosstm/trunk/XTS/demo/docs/wherenext.xml
===================================================================
--- labs/jbosstm/trunk/XTS/demo/docs/wherenext.xml 2008-08-27 12:48:59 UTC (rev 21931)
+++ labs/jbosstm/trunk/XTS/demo/docs/wherenext.xml 2008-08-27 13:23:50 UTC (rev 21932)
@@ -16,7 +16,7 @@
MA 02110-1301, USA.
- (C) 2005-2006,
+ (C) 2005-2008,
@author JBoss Inc.
-->
<page title="XML Transaction Service Demonstration Application: Where next?" rootpath="../..">
@@ -36,7 +36,7 @@
<html>
<p>
For further information, please consult the XML Transaction component of JBossTS 4.3.0 product documentation set.
- <li><a class="linkscoloured" href="../../docs/Programmers Guide.pdf" target="_blank">Programmers Guide</a> (.pdf)</li>
+ <li><a class="linkscoloured" href="../../docs/ProgrammersGuide.pdf" target="_blank">Programmers Guide</a> (.pdf)</li>
</p>
<p>
A collection of links to additional background reading material on Web services coordination and transactions is also avaialble on the JBossTS labs site:
Modified: labs/jbosstm/trunk/XTS/demo/xsl/ATL_LookAndFeel.xsl
===================================================================
--- labs/jbosstm/trunk/XTS/demo/xsl/ATL_LookAndFeel.xsl 2008-08-27 12:48:59 UTC (rev 21931)
+++ labs/jbosstm/trunk/XTS/demo/xsl/ATL_LookAndFeel.xsl 2008-08-27 13:23:50 UTC (rev 21932)
@@ -640,23 +640,11 @@
Copyright 2002-2005 Arjuna Technologies
- <xsl:element name="IMG">
- <xsl:attribute name="src"><xsl:value-of select="$rootpath"/>/images/look_and_feel/spacer.jpg</xsl:attribute>
- <xsl:attribute name="alt"></xsl:attribute>
- <xsl:attribute name="border">0</xsl:attribute>
- </xsl:element>
+ <br/>Copyright 2005-2008 JBoss Inc.
- All Rights Reserved.
+ <br/>All Rights Reserved.
- <br/><a class="linkscoloured" href="mailto:info at arjuna.com">info at arjuna.com</a>
-
- <xsl:element name="IMG">
- <xsl:attribute name="src"><xsl:value-of select="$rootpath"/>/images/look_and_feel/spacer.jpg</xsl:attribute>
- <xsl:attribute name="alt"></xsl:attribute>
- <xsl:attribute name="border">0</xsl:attribute>
- </xsl:element>
-
- +44 191 243 0676
+ <br/><a class="linkscoloured" href="http://www.jboss.org/jbosstm/">http://www.jboss.org/jbosstm/</a>
</FONT>
</TD>
</TR>
Modified: labs/jbosstm/trunk/XTS/docs/XTSRecoveryNotes.txt
===================================================================
--- labs/jbosstm/trunk/XTS/docs/XTSRecoveryNotes.txt 2008-08-27 12:48:59 UTC (rev 21931)
+++ labs/jbosstm/trunk/XTS/docs/XTSRecoveryNotes.txt 2008-08-27 13:23:50 UTC (rev 21932)
@@ -38,8 +38,7 @@
associated with the WS-AT transaction manager class.
Volatile participants are not expected to be involved in
-commit/rollback or recovery processing (even though they implement
-commit(), rollback() and unknown() these should never be called). They
+commit/rollback or recovery processing. They
are expected to perform any necessary saving or flushing of volatile
state at prepare and, if necessary, delete any redundant in-memory or
persistent state at the same time. They must vote against prepare if
More information about the jboss-svn-commits
mailing list