[jboss-svn-commits] JBL Code SVN: r18846 - labs/jbosstm/trunk/XTS/demo/docs.
jboss-svn-commits at lists.jboss.org
jboss-svn-commits at lists.jboss.org
Tue Mar 11 13:35:28 EDT 2008
Author: adinn
Date: 2008-03-11 13:35:28 -0400 (Tue, 11 Mar 2008)
New Revision: 18846
Modified:
labs/jbosstm/trunk/XTS/demo/docs/about.xml
labs/jbosstm/trunk/XTS/demo/docs/deploying.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/wherenext.xml
Log:
modified trail map for 4.3.0 -- implements last remaining changes required for JBTM-16 -- this time it really is all of them -- and also more of the changes required for JBTM-123
Modified: labs/jbosstm/trunk/XTS/demo/docs/about.xml
===================================================================
--- labs/jbosstm/trunk/XTS/demo/docs/about.xml 2008-03-11 17:34:01 UTC (rev 18845)
+++ labs/jbosstm/trunk/XTS/demo/docs/about.xml 2008-03-11 17:35:28 UTC (rev 18846)
@@ -36,7 +36,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.2.2 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.3.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,
@@ -51,6 +51,10 @@
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.
+ </p>
+ <p>
Full source code for the services and the client is included, along with an ant script for building and deploying the code.
The following step of this trail map will show you how to deploy and run the application.
</p>
Modified: labs/jbosstm/trunk/XTS/demo/docs/deploying.xml
===================================================================
--- labs/jbosstm/trunk/XTS/demo/docs/deploying.xml 2008-03-11 17:34:01 UTC (rev 18845)
+++ labs/jbosstm/trunk/XTS/demo/docs/deploying.xml 2008-03-11 17:35:28 UTC (rev 18846)
@@ -35,46 +35,51 @@
<area title="Deploying the sample application">
<html>
<p>
- To run the demonstration application, you must compile the source code; bundle it, along with the required metadata files, into appropriate deployment constructs and then deploy these into the application container. This process is somewhat involved, but fortunately is completely automated by an ant build script.
+ To run the sample application, you must compile the source code; bundle it, along with the required metadata files, into appropriate deployment constructs and then deploy these into the application container. This process is somewhat involved, but fortunately is completely automated by an ant build script.
</p>
<p>
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>
- Deploying into JBoss.
+ This release has been tested against JBoss 4.2.2.GA and JBoss 5.0.Beta4.
+ </p>
+ <p>
+ Deploying into JBoss 4.2.
</p>
- <p>
- This release has been tested against JBoss 4.0.3SP1, 4.0.4GA and 4.0.5GA.
- </p>
<ol>
- <li><p>Install JBoss.</p>
+ <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>, <code>JBOSS_PORT</code>, <code>JBOSS_URLSTUB</code>, <code>JBOSS_DEPLOY_DIR</code> and <code>JBOSS_HOME</code> variables to reflect the location 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>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>
- Deploying into webMethods.
- </p>
- <p>
- This release has been tested against webMethods 5.0.2.
- </p>
- <p>
- N.B. The classpath used to run webMethods must be modified so that the stax-api.1.0.jar contained within this distribution is encountered prior to all other webMethods jars.
+ 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>
- <ol>
- <li><p>Install webMethods.</p>
- </li>
- <li><p>Edit the <code><xts-home>/demo/webmethods.properties</code> file, replacing the <code>WEBMETHODS_HOSTNAME</code>, <code>WEBMETHODS_PORT</code>, <code>WEBMETHODS_URLSTUB</code>, <code>WEBMETHODS_DEPLOY_DIR</code> and <code>WEBMETHODS_HOME</code> variables to reflect the location of your webMethods installation</p></li>
- <li><p>Compile the application source, build the application archive file and deploy it into webMethods deploy directory by typing '<code>build.sh webmethods clean deploy</code>' on Unix or '<code>build.bat webmethods clean deploy</code>' on Windows</p></li>
- <li><p>Run the application from the deploy directory by using the webMethods runapp 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>
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.
+ </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>
+ <li><p>Edit the <code><xts-home>/demo/jboss.properties</code> file, replacing the <code>JBOSS_HOSTNAME</code>, <code>JBOSS_PORT</code>, <code>JBOSS_URLSTUB</code>, <code>JBOSS_DEPLOY_DIR</code> and <code>JBOSS_HOME</code> variables to reflect the location 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>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>deploy</code>' in the commands listed above with the alternative target '<code>deployrpc</code>'
+ </p>
<p>Using the application</p>
<ul>
<li><p>When invoked, the client will attempt to begin a transaction, reserve theatre tickets, a restaurant table and a taxi according to the parameters you have selected, then commit the transaction. It will log each step of its activity to the console window. As the transaction proceeds, each of the Web Services will pop up a window of its own in which its state and activity log can be seen. Some events in the service code are also logged to the console.</p></li>
Modified: labs/jbosstm/trunk/XTS/demo/docs/index.xml
===================================================================
--- labs/jbosstm/trunk/XTS/demo/docs/index.xml 2008-03-11 17:34:01 UTC (rev 18845)
+++ labs/jbosstm/trunk/XTS/demo/docs/index.xml 2008-03-11 17:35:28 UTC (rev 18846)
@@ -33,7 +33,7 @@
<area title="Introduction">
<html>
<p>
- Welcome to the "Night Out" sample application for the XML Transaction component of JBossTS 4.2.2.
+ Welcome to the "Night Out" sample application for the XML Transaction component of JBossTS 4.3.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-03-11 17:34:01 UTC (rev 18845)
+++ labs/jbosstm/trunk/XTS/demo/docs/installcontent.xml 2008-03-11 17:35:28 UTC (rev 18846)
@@ -34,7 +34,7 @@
<area title="Installation Content">
<html>
<p>
- The installer should have installed the following directories under <jbosst 4.2.2 install>/wst directory:
+ The installer should have installed the following directories under <jbosst 4.3.0 install>/wst directory:
<ul>
<p>conf: product configuration files.</p>
<p>coordinator: an application independent version of the transaction coordinator.</p>
@@ -46,13 +46,13 @@
</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.2.2 is designed to run within JBoss and webMethods.
+ This release of the XML Transaction component of JBossTS 4.3.0 is designed to run within JBoss.
</p>
<p>
- This release has been tested on JBoss 4.0.3SP1, 4.0.4GA, 4.0.5GA and webMethods 5.0.2.
+ This release has been tested on JBoss 4.2.2.GA and JBoss 5.0.Beta4.
</p>
<p>
- To compile, deploy and run the sample application we also recommend using java SDK 1.4.2 and Apache ant 1.6.1 or later.
+ To compile, deploy and run the sample application we also recommend using java SDK 1.5 and Apache ant 1.6.1 or later.
If you do not already have these, you can download them from <a class="linkscoloured" href="http://java.sun.com/">java website</a> and the <a class="linkscoloured" href="http://ant.apache.org/">ant website</a>.
</p>
</html>
Modified: labs/jbosstm/trunk/XTS/demo/docs/sourcecode.xml
===================================================================
--- labs/jbosstm/trunk/XTS/demo/docs/sourcecode.xml 2008-03-11 17:34:01 UTC (rev 18845)
+++ labs/jbosstm/trunk/XTS/demo/docs/sourcecode.xml 2008-03-11 17:35:28 UTC (rev 18846)
@@ -35,7 +35,9 @@
<area title="Source code overview">
<html>
<p>
- You can begin experimenting with the XML Transaction component of JBoss 4.2.2 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.2.2 install>/wst/demo/src directory.
+ 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).
</p>
<p>
It is structured as follows:
@@ -44,62 +46,71 @@
<ul>
<li>
<p>
- com/arjuna/xts/nightout/clients/
+ com/jboss/jbosstm/xts/demo/
</p>
<ul>
<li>
<p>
- jboss/BasicClient.java: A servlet that processes the form input and runs either an Atomic Transaction or Business Activity to make the bookings.
+ client/BasicClient.java:
</p>
<p>
- This servlet uses the JBoss JAX-RPC implementation as the SOAP transport library.
+ A servlet that processes the form input and runs either an Atomic Transaction (AT) or Business Activity (BA) to make the bookings.
</p>
- </li>
- <li>
<p>
- jboss/restaurant/* : JBoss JAX-RPC client interfaces for accessing the restaurant web services.
+ This servlet uses the JBossWS JaxWS implementation as the SOAP transport library.
</p>
- </li>
- <li>
<p>
- jboss/taxi/* : JBoss JAX-RPC client interfaces for accessing the taxi web services.
+ Method configureClientHandler installs the JBoss handler on the JaxWS service endpoint proxies. This ensurs that the client's AT or BA transaction
+ context is propagated to the web services when their remote methods are invoked.
</p>
</li>
<li>
<p>
- jboss/theatre/* : JBoss JAX-RPC client interfaces for accessing the theatre web services.
+ restaurant/* :
</p>
+ <p>
+ JaxWS client interfaces for accessing the remote restaurant web services via JaxWS service proxies.
+ </p>
</li>
<li>
<p>
- weblogic/BasicClient.java: A servlet that processes the form input and runs either an Atomic Transaction or Business Activity to make the bookings.
+ taxi/* :
</p>
<p>
- This servlet uses the WebLogic JAX-RPC implementation as the SOAP transport library.
+ JaxWS client interfaces for accessing the remote taxi web services via JaxWS service proxies.
</p>
</li>
<li>
<p>
- weblogic/proxies/* : WebLogic JAX-RPC client side code for accessing the Web services. This is automatically generated code.
+ theatre/* :
</p>
+ <p>
+ JaxWS client interfaces for accessing the remote theatre web services via JaxWS service proxies.
+ </p>
</li>
<li>
<p>
- webmethods/BasicClient.java: A servlet that processes the form input and runs either an Atomic Transaction or Business Activity to make the bookings.
+ services/[restuarant|taxi|theatre]/* :
</p>
- </li>
- </ul>
- </li>
- <li>
- <p>
- com/arjuna/xts/nightout/services/[Restuarant|Taxi|Theatre]/
- </p>
- <ul>
- <li>
+ <p>
+ JaxWS service endpoint implementation classes
+ </p>
<p>Each of these three Web services has similar structure, featuring a *Manager.java class (the transactional business logic, knowing nothing of Web services),
- a *View.java file (the GUI component, largely tool generated), and the files that expose the business logic as transactional Web services.
- In the filenames, AT denotes Atomic Transaction, whilst BA is for Business Activities. The *Service.java file is the business interface, whilst the *Participant.java file has the transaction management code.
+ a *View.java file (the GUI component, largely tool generated), and the files that expose the business logic as transactional JaxWS Web services.
</p>
+ <p>
+ In the filenames, AT denotes Atomic Transaction, whilst BA is for Business Activities.
+ </p>
+ <p>
+ The *ServiceAT/BA.java file is the business interface, whilst the *Participant.java file has the transaction management code.
+ </p>
+ <p>
+ The *ServiceAT/BA classes expose their JaxWS SEI methods using '<code>javax.jws.WebService</code>' and '<code>javax.jws.WebMethod</code>' annotations.
+ </p>
+ <p>
+ A '<code>javax.jws.HandlerChain</code>' annotation identifies a handler chain deployment descriptor file deployed with the demo applciation. This decriptor configures
+ the services with handlers that run SEI method invocations in the transaction context propagated from the client.
+ </p>
</li>
</ul>
</li>
Modified: labs/jbosstm/trunk/XTS/demo/docs/wherenext.xml
===================================================================
--- labs/jbosstm/trunk/XTS/demo/docs/wherenext.xml 2008-03-11 17:34:01 UTC (rev 18845)
+++ labs/jbosstm/trunk/XTS/demo/docs/wherenext.xml 2008-03-11 17:35:28 UTC (rev 18846)
@@ -34,7 +34,7 @@
<area title="Where next?">
<html>
<p>
- For further information, please consult the XML Transaction component of JBossTS 4.2.2 product documentation set.
+ 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>
</p>
<p>
More information about the jboss-svn-commits
mailing list