[jboss-svn-commits] JBL Code SVN: r29841 - labs/jbosstm/enterprise/tags/EAP_5_0_0/Transactions_Failure_Recovery_Guide/en-US.
jboss-svn-commits at lists.jboss.org
jboss-svn-commits at lists.jboss.org
Wed Oct 28 03:09:57 EDT 2009
Author: laubai
Date: 2009-10-28 03:09:57 -0400 (Wed, 28 Oct 2009)
New Revision: 29841
Modified:
labs/jbosstm/enterprise/tags/EAP_5_0_0/Transactions_Failure_Recovery_Guide/en-US/Architecture_of_the_Recovery_Manager.xml
Log:
Added changes for JBPAPP-2984.
Modified: labs/jbosstm/enterprise/tags/EAP_5_0_0/Transactions_Failure_Recovery_Guide/en-US/Architecture_of_the_Recovery_Manager.xml
===================================================================
--- labs/jbosstm/enterprise/tags/EAP_5_0_0/Transactions_Failure_Recovery_Guide/en-US/Architecture_of_the_Recovery_Manager.xml 2009-10-28 06:54:44 UTC (rev 29840)
+++ labs/jbosstm/enterprise/tags/EAP_5_0_0/Transactions_Failure_Recovery_Guide/en-US/Architecture_of_the_Recovery_Manager.xml 2009-10-28 07:09:57 UTC (rev 29841)
@@ -48,7 +48,7 @@
On initialization the Recovery Manager first loads in configuration information via a properties file. This configuration includes a number of recovery activators and recovery modules, which are then dynamically loaded.
</para>
<para>
- Since the version 3.0 of JBossTS, the Recovery Manager is not specifically tied to an Object Request Broker or ORB. Hence, the OTS recovery protocol is not implicitly enabled. To enable such protocol, we use the concept of recovery activator, defined with the interface <interfacename>RecoveryActivator</interfacename>, which is used to instantiate a recovery class related to the underlying communication protocol. For instance, when used with OTS, the <interfacename>RecoveryActivitor</interfacename> has the responsibility to create a RecoveryCoordinator object able to respond to the replay_completion operation.
+ Since the version 3.0 of JBossTS, the Recovery Manager is not specifically tied to an Object Request Broker or ORB. Hence, the OTS recovery protocol is not implicitly enabled. To enable such protocol, we use the concept of recovery activator, defined with the interface <interfacename>RecoveryActivator</interfacename>, which is used to instantiate a recovery class related to the underlying communication protocol. For instance, when used with OTS, the <interfacename>RecoveryActivator</interfacename> has the responsibility to create a RecoveryCoordinator object able to respond to the replay_completion operation.
</para>
<para>
All <interfacename>RecoveryActivator</interfacename> instances inherit the same interface. They are loaded via the following recovery extension property:
@@ -127,7 +127,7 @@
</listitem>
<listitem>
<para>
- RecActivatorLoader: Dynamically loads in the RecoveryActivator specified in the Recovery Manager property file. Each RecoveryActicator is specified as a recovery extension in the properties file.
+ RecActivatorLoader: Dynamically loads in the RecoveryActivator specified in the Recovery Manager property file. Each RecoveryActivator is specified as a recovery extension in the properties file.
</para>
</listitem>
<listitem>
More information about the jboss-svn-commits
mailing list