[jboss-svn-commits] JBL Code SVN: r35440 - labs/jbosstm/trunk/XTS/docs/Transactions_XTS_Programmers_Guide/en-US/extras.

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

Author: misty at redhat.com
Date: 2010-10-05 19:06:25 -0400 (Tue, 05 Oct 2010)
New Revision: 35440

Added:
   labs/jbosstm/trunk/XTS/docs/Transactions_XTS_Programmers_Guide/en-US/extras/#example-XTSBARecoveryModule.java#
   labs/jbosstm/trunk/XTS/docs/Transactions_XTS_Programmers_Guide/en-US/extras/example-xts-jboss-beans-wsc-environment-bean.xml
Log:
(Re?)-added changes to Stand-Alone Coordination for XTS.

Added: labs/jbosstm/trunk/XTS/docs/Transactions_XTS_Programmers_Guide/en-US/extras/#example-XTSBARecoveryModule.java#
===================================================================
--- labs/jbosstm/trunk/XTS/docs/Transactions_XTS_Programmers_Guide/en-US/extras/#example-XTSBARecoveryModule.java#	                        (rev 0)
+++ labs/jbosstm/trunk/XTS/docs/Transactions_XTS_Programmers_Guide/en-US/extras/#example-XTSBARecoveryModule.java#	2010-10-05 23:06:25 UTC (rev 35440)
@@ -0,0 +1,29 @@
++public interface XTSBARecoveryModule
+  {
+      public BusinessAgreementWithParticipantCompletionParticipant
+          deserializeParticipantCompletionParticipant(String id,
+@@ -16,4 +16,5 @@
+          recreateCoordinatorCompletionParticipant(String id,
+                                                   byte[] recoveryState)
+          throws Exception;
++    public void endScan();
+  }
+public interface XTSATRecoveryModule
+{
+    public BusinessAgreementWithParticipantCompletionParticipant
+	deserializeParticipantCompletionParticipant(String id,
+						    ObjectInputStream stream)
+	throws Exception;
+    public BusinessAgreementWithParticipantCompletionParticipant
+	recreateParticipantCompletionParticipant(String id,
+						 byte[] recoveryState)
+	throws Exception;
+    public BusinessAgreementWithCoordinatorCompletionParticipant
+	deserializeCoordinatorCompletionParticipant(String id,
+						    ObjectInputStream stream)
+	throws Exception;
+    public BusinessAgreementWithCoordinatorCompletionParticipant
+	recreateCoordinatorCompletionParticipant(String id,
+						 byte[] recoveryState)
+	throws Exception;
+}

Added: labs/jbosstm/trunk/XTS/docs/Transactions_XTS_Programmers_Guide/en-US/extras/example-xts-jboss-beans-wsc-environment-bean.xml
===================================================================
--- labs/jbosstm/trunk/XTS/docs/Transactions_XTS_Programmers_Guide/en-US/extras/example-xts-jboss-beans-wsc-environment-bean.xml	                        (rev 0)
+++ labs/jbosstm/trunk/XTS/docs/Transactions_XTS_Programmers_Guide/en-US/extras/example-xts-jboss-beans-wsc-environment-bean.xml	2010-10-05 23:06:25 UTC (rev 35440)
@@ -0,0 +1,44 @@
+<bean name="XTS:WSCEnvironmentBean" class="org.jboss.jbossts.xts.environment.WSCEnvironmentBean">
+  <constructor factoryClass="org.jboss.jbossts.xts.environment.XTSPropertyManager"
+               factoryMethod="getWSCEnvironmentBean"/>
+  <!-- we need the bind address and port from jboss web -->
+  <depends>jboss.web:service=WebServer</depends>
+  <depends>jboss:service=TransactionManager</depends>
+  . . .
+  <!--
+      if you want to use a coordinator running in a remote JVM then you can
+      simply configure the URL. This will also be necessary if you are using
+      a non-JBoss coordination service.
+      
+      <property name="coordinatorURL11">
+         <value>http://10.0.1.99:8080/ws-c11/ActivationService</value>
+      </property>
+  -->
+  <!--
+      if you are using a remote JBoss XTS coordinator you can just redefine
+      the scheme, address, port or path to the desired value and the ones
+      left undefined will be defaulted to use the standard XTS coordinator
+      URL elements. So, for example if your XTS coordinator services is
+      deployed in another AS on host myhost.myorg.com you only need to define
+      property coordinatorAddress11 to have value myhost.myorg.com and the
+      coordinator address used by clients will be
+      http://myhost.myorg.com:8080/ws-c11/ActivationService n.b. if the remote
+      machine is using JBoss XTS then you won't want to redefine the port
+      unless you have monkeyed around with the port config in the remote AS. also
+      you won't need to change the path unless you have tweaked the deployment
+      descriptor to relocate the XTS services.
+
+      <property name="coordinatorScheme11">
+         <value>http</value>
+      </property>
+      <property name="coordinatorAddress11">
+         <value>10.0.1.99</value>
+      </property>
+      <property name="coordinatorPort11">
+         <value>9191</value>
+      </property>
+      <property name="coordinatorPath11">
+         <value>ws-c11/ActivationService</value>
+      </property>
+  -->
+</bean>