[jboss-svn-commits] JBL Code SVN: r18208 - labs/jbosstm/workspace/adinn/XTSGF.

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

Author: adinn
Date: 2008-01-30 10:56:52 -0500 (Wed, 30 Jan 2008)
New Revision: 18208

Modified:
   labs/jbosstm/workspace/adinn/XTSGF/README
Log:
modified instructions to build demo which can exercise btoh WSCOOR 1.0 and 1.1

Modified: labs/jbosstm/workspace/adinn/XTSGF/README
===================================================================
--- labs/jbosstm/workspace/adinn/XTSGF/README	2008-01-30 15:38:54 UTC (rev 18207)
+++ labs/jbosstm/workspace/adinn/XTSGF/README	2008-01-30 15:56:52 UTC (rev 18208)
@@ -1,14 +1,25 @@
 This tree includes a prototype implementation of WSCOOR 1.1
 specification built over JaxWS as implemented in Glassfish V2.0
 (release v2b58g). It successfully implements the WSCOOR, WSAT and WSBA
-protocols, exposing them via JaxWS services.
+protocols as JaxWS services. It also retains the existing WSCOOR, WSAT
+and WSBA 1.0 implementation which employ a JBossTS native soap
+stack. This version of XTS allows the 1.0 and 1.1 wscoor services to
+operate side by side. The configuration files for the 1.0 services are
+wst.xml, wstx.xml and wscf.xml. Those for the 1.1. services are
+wst11.xml, wstx11.xml and wscf11.xml. Clients import API classes from
+packages com.arjuna.mw.wst and com.arjuna.mw.wst11 in order to employ
+the 1.0 or 1.1 implementation respectively.
 
-This version of XTS allows the 1.0 and 1.1 services to operate side by
-side. The configuration files for the 1.0 services are wst.xml,
-wstx.xml and wscf.xml. Those for the 1.1. services are wst11.xml,
-wstx11.xml and wscf11.xml. The current demo employs the 1.1. services
-and, accordingly, uses the 1.1 versions of Transactionfactory,
-Transaction, BusinessActivityFactory, etc in the WSTX/.../wst tree.
+The demo directory implements two versions of the demo program. The
+client and services in demo/src11 employ the wscoor 1.1 services (and,
+accordingly, uses the 1.1 versions of Transactionfactory, Transaction,
+BusinessActivityFactory, etc in the WSTX/.../wst tree). The client and
+services in demo/src use the 1.0 services. The 1.1 based demo client
+invokes its web services uing JaxWS while the 1.0 based demo client
+invokes web services using JaxRPC. The build scripts for the demo tree
+produce an EAR deliverable which bundles both WSCOOR implementations
+and both demo programs. Unfortunately, at present, due to a bug in
+Glassfish, the JaxRPC based implementation will not deploy correctly.
 
 In order to build this implementation (and its associated demo
 program) you need first to download a JBossTS source tree, build it
@@ -19,16 +30,20 @@
 installed Glassfish V2.0 release.
 
 The next step is to modify the file jboss.properties in directory demo
-so that localhost, 8080 and xtsdemowebservcies as the JBoss host, port
-and url stub for the demo.
+so that localhost, 8080 and xtsdemowebservices are configured as the
+JBoss host, port and url stub for the demo. Note that this defines the
+location of both the 1.0 demo web services (this defaults to
+http://localhost:8080/xtsdemowebservices) and the 1.1 demo web
+services (defaults to http://localhost:8080/xtsdemowebservices11).
 
-The final steps require executing the following commands:
+The final steps require executing the following commands from the root
+of this source tree:
 
   ant clean install
   cd xts-install/demo
   bash jboss clean build
 
-This will generate a deployable ear file
+This will generate an EAR file
 
     xts-install/demo/build/xts-demo.ear
 
@@ -37,7 +52,12 @@
 
   http://localhost:4848/
 
-The demo may be invoked from the usual web form
+The 1.0 WSCOOR based demo may be invoked from the web form page at
+
+  http://localhost:8080/xts-demo/
+
+The 1.1 WSCOOR based based demo may be invoked from usual web form
 page at
 
-  http://localhost:8080/xts-demo/
+  http://localhost:8080/xts-demo11/
+