[jboss-cvs] JBossAS SVN: r77395 - in projects/docs/enterprise: 4.3.3/Transactions/Transactions_Failure_Recovery_Guide/en-US and 1 other directory.

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

Author: irooskov at redhat.com
Date: 2008-08-24 22:20:21 -0400 (Sun, 24 Aug 2008)
New Revision: 77395

Modified:
   projects/docs/enterprise/4.3.3/Transactions/Transactions_Failure_Recovery_Guide/en-US/How_JBossTS_managers_the_OTS_Recovery_Protocol.xml
   projects/docs/enterprise/4.3/Transactions/Transactions_Failure_Recovery_Guide/en-US/How_JBossTS_managers_the_OTS_Recovery_Protocol.xml
Log:
adding sentence re-write that was done in order to resolve RT #26532


Modified: projects/docs/enterprise/4.3/Transactions/Transactions_Failure_Recovery_Guide/en-US/How_JBossTS_managers_the_OTS_Recovery_Protocol.xml
===================================================================
--- projects/docs/enterprise/4.3/Transactions/Transactions_Failure_Recovery_Guide/en-US/How_JBossTS_managers_the_OTS_Recovery_Protocol.xml	2008-08-25 02:13:51 UTC (rev 77394)
+++ projects/docs/enterprise/4.3/Transactions/Transactions_Failure_Recovery_Guide/en-US/How_JBossTS_managers_the_OTS_Recovery_Protocol.xml	2008-08-25 02:20:21 UTC (rev 77395)
@@ -175,7 +175,7 @@
 			</listitem>
 		</itemizedlist>
 		<para>
-			It appears that to redirect replay_completion invocations to a default servant we need  to create a POA with the Request Processing policy assigned with the value set to USE_DEFAULT_SERVANT. However to reach that default Servant we should first reach the POA that forward the request to the default servant. Indeed, the ORB uses a set of information to retrieve a POA; these information are contained in the object reference used by the client. Among these information there are the IP address and the port number where resides the server and also the POA name. To perform replay_completion invocations, the solution adopted by JBossTS is to provide one Servant, per machine, and located in the RecoveryManager process, a separate process from client or server applications. The next section explains how the indirection to a default Servant located on a separate process is provided for ORBIX and for JacORB. 
+			It appears that to redirect replay_completion invocations to a default servant we need  to create a POA with the Request Processing policy assigned with the value set to USE_DEFAULT_SERVANT. However to reach that default Servant we should first reach the POA that forward the request to the default servant. Indeed, the ORB uses a set of information to retrieve a POA; these information are contained in the object reference used by the client. Among these information there are the IP address and the port number where resides the server and also the POA name. JBossTS provides one servant per machine to perform replay_completion invocations. This servant is located in the RecoveryManager process. The RecoveryManager process is a separate process from the client and server applications. The next section explains how the indirection to a default Servant located on a separate process is provided for ORBIX and for JacORB. 
 		</para>
 	</section>
 	<section id="sect-Transactions_Failure_Recovery_Guide-How_JBossTS_manages_the_OTS_Recovery_Protocol-The_default_RecoveryCoordinator_in_Orbix">

Modified: projects/docs/enterprise/4.3.3/Transactions/Transactions_Failure_Recovery_Guide/en-US/How_JBossTS_managers_the_OTS_Recovery_Protocol.xml
===================================================================
--- projects/docs/enterprise/4.3.3/Transactions/Transactions_Failure_Recovery_Guide/en-US/How_JBossTS_managers_the_OTS_Recovery_Protocol.xml	2008-08-25 02:13:51 UTC (rev 77394)
+++ projects/docs/enterprise/4.3.3/Transactions/Transactions_Failure_Recovery_Guide/en-US/How_JBossTS_managers_the_OTS_Recovery_Protocol.xml	2008-08-25 02:20:21 UTC (rev 77395)
@@ -175,7 +175,7 @@
 			</listitem>
 		</itemizedlist>
 		<para>
-			It appears that to redirect replay_completion invocations to a default servant we need  to create a POA with the Request Processing policy assigned with the value set to USE_DEFAULT_SERVANT. However to reach that default Servant we should first reach the POA that forward the request to the default servant. Indeed, the ORB uses a set of information to retrieve a POA; these information are contained in the object reference used by the client. Among these information there are the IP address and the port number where resides the server and also the POA name. To perform replay_completion invocations, the solution adopted by JBossTS is to provide one Servant, per machine, and located in the RecoveryManager process, a separate process from client or server applications. The next section explains how the indirection to a default Servant located on a separate process is provided for ORBIX and for JacORB. 
+			It appears that to redirect replay_completion invocations to a default servant we need  to create a POA with the Request Processing policy assigned with the value set to USE_DEFAULT_SERVANT. However to reach that default Servant we should first reach the POA that forward the request to the default servant. Indeed, the ORB uses a set of information to retrieve a POA; these information are contained in the object reference used by the client. Among these information there are the IP address and the port number where resides the server and also the POA name. JBossTS provides one servant per machine to perform replay_completion invocations. This servant is located in the RecoveryManager process. The RecoveryManager process is a separate process from the client and server applications. The next section explains how the indirection to a default Servant located on a separate process is provided for ORBIX and for JacORB. 
 		</para>
 	</section>
 	<section id="sect-Transactions_Failure_Recovery_Guide-How_JBossTS_manages_the_OTS_Recovery_Protocol-The_default_RecoveryCoordinator_in_Orbix">