[jboss-svn-commits] JBL Code SVN: r23939 - labs/jbosstm/enterprise/tags/EAP_4_3_0/Transactions_Failure_Recovery_Guide/zh-CN.
jboss-svn-commits at lists.jboss.org
jboss-svn-commits at lists.jboss.org
Tue Nov 18 23:51:55 EST 2008
Author: xhuang at jboss.com
Date: 2008-11-18 23:51:54 -0500 (Tue, 18 Nov 2008)
New Revision: 23939
Modified:
labs/jbosstm/enterprise/tags/EAP_4_3_0/Transactions_Failure_Recovery_Guide/zh-CN/Architecture_of_the_Recovery_Manager.po
labs/jbosstm/enterprise/tags/EAP_4_3_0/Transactions_Failure_Recovery_Guide/zh-CN/How_JBossTS_managers_the_OTS_Recovery_Protocol.po
Log:
update
Modified: labs/jbosstm/enterprise/tags/EAP_4_3_0/Transactions_Failure_Recovery_Guide/zh-CN/Architecture_of_the_Recovery_Manager.po
===================================================================
--- labs/jbosstm/enterprise/tags/EAP_4_3_0/Transactions_Failure_Recovery_Guide/zh-CN/Architecture_of_the_Recovery_Manager.po 2008-11-19 04:51:54 UTC (rev 23938)
+++ labs/jbosstm/enterprise/tags/EAP_4_3_0/Transactions_Failure_Recovery_Guide/zh-CN/Architecture_of_the_Recovery_Manager.po 2008-11-19 04:51:54 UTC (rev 23939)
@@ -7,7 +7,7 @@
"Project-Id-Version: Architecture_of_the_Recovery_Manager\n"
"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
"POT-Creation-Date: 2008-09-23 06:30+0000\n"
-"PO-Revision-Date: 2008-11-11 20:00+1000\n"
+"PO-Revision-Date: 2008-11-19 14:51+1000\n"
"Last-Translator: \n"
"Language-Team: <en at li.org>\n"
"MIME-Version: 1.0\n"
@@ -1310,7 +1310,7 @@
#: Architecture_of_the_Recovery_Manager.xml:440
#, no-c-format
msgid "Expired Scanner Thread"
-msgstr ""
+msgstr "Expired Scanner 线程"
#. Tag: para
#: Architecture_of_the_Recovery_Manager.xml:441
@@ -1320,7 +1320,7 @@
"ExpiryEntryMonitor is created which is used to remove long dead items from "
"the ObjectStore. A number of scanner modules are dynamically loaded which "
"remove long dead items for a particular type."
-msgstr ""
+msgstr "当切换管理者初始化 expiry scanner 线程时，ExpiryEntryMonitor 将被创建并用来从对象库中删除长时间失效的条目。一些用于删除特殊类型条目的扫描器模块也被动态地加载。"
#. Tag: para
#: Architecture_of_the_Recovery_Manager.xml:444
@@ -1328,7 +1328,7 @@
msgid ""
"Scanner modules are loaded at initialisation and are specified as properties "
"beginning with"
-msgstr ""
+msgstr "扫描器模块在初始化时被加载且被指定为如下的属性："
#. Tag: screen
#: Architecture_of_the_Recovery_Manager.xml:447
@@ -1337,6 +1337,8 @@
"com.arjuna.ats.arjuna.recovery.expiryScanner<Scanner Name>=<Scanner "
"Class>"
msgstr ""
+"com.arjuna.ats.arjuna.recovery.expiryScanner<Scanner Name>=<Scanner "
+"Class>"
#. Tag: para
#: Architecture_of_the_Recovery_Manager.xml:448
@@ -1344,13 +1346,13 @@
msgid ""
"All the scanner modules are called periodically to scan for dead items by "
"the ExpiryEntryMonitor thread. This period is set with the property:"
-msgstr ""
+msgstr "所有的扫描器模块都定期地被 ExpiryEntryMonitor 线程调用来扫描无效条目。时间间隔用如下属性指定："
#. Tag: screen
#: Architecture_of_the_Recovery_Manager.xml:451
#, no-c-format
msgid "com.arjuna.ats.arjuna.recovery.expiryScanInterval"
-msgstr ""
+msgstr "com.arjuna.ats.arjuna.recovery.expiryScanInterval"
#. Tag: para
#: Architecture_of_the_Recovery_Manager.xml:452
@@ -1358,7 +1360,7 @@
msgid ""
"All scanners inherit the same behaviour from the java interface "
"<interfacename>ExpiryScanner</interfacename> as illustrated in diagram below:"
-msgstr ""
+msgstr "如下图所示，所有的扫描器都从 Java 接口 <interfacename>ExpiryScanner</interfacename> 继承相同的行为："
#. Tag: para
#: Architecture_of_the_Recovery_Manager.xml:460
@@ -1366,7 +1368,7 @@
msgid ""
"A scan method is provided by this interface and implemented by all scanner "
"modules, this is the method that gets called by the scanner thread."
-msgstr ""
+msgstr "这个接口提供一个 scan 方法，它被所有扫描器模块实现，它是扫描器线程所调用的方法。"
#. Tag: para
#: Architecture_of_the_Recovery_Manager.xml:463
@@ -1376,25 +1378,25 @@
"TransactionStatusManagerItems from the Object Store. These items will remain "
"in the Object Store for a period of time before they are deleted. This time "
"is set by the property:"
-msgstr ""
+msgstr "ExpiredTransactionStatusManagerScanner 从对象库里删除长时间无效的 TransactionStatusManagerItems。在被删除之前，这些条目将保留在对象库一段时间。这个时间用如下属性设置："
#. Tag: screen
#: Architecture_of_the_Recovery_Manager.xml:466
#, no-c-format
msgid "com.arjuna.ats.arjuna.recovery.transactionStatusManagerExpiryTime"
-msgstr ""
+msgstr "com.arjuna.ats.arjuna.recovery.transactionStatusManagerExpiryTime"
#. Tag: para
#: Architecture_of_the_Recovery_Manager.xml:467
#, no-c-format
msgid "(default 12 hours)"
-msgstr ""
+msgstr "（缺省为 12 个小时）"
#. Tag: title
#: Architecture_of_the_Recovery_Manager.xml:472
#, no-c-format
msgid "Application Process"
-msgstr ""
+msgstr "应用程序进程"
#. Tag: para
#: Architecture_of_the_Recovery_Manager.xml:473
@@ -1406,18 +1408,19 @@
"Recovery Manager needs access to the transaction tables so that it can "
"determine whether a transaction is still in progress, if so then recovery "
"does not happen."
-msgstr ""
+msgstr "它代表用户的事务性程序。应用程序进程维护的本地事务表（Hash）跟踪该进程创建的所有事务的当前状态，切换管理者需要访问这个事务表来获知某个事务是否仍然在运行，如果是，那么切换不会进行。"
#. Tag: para
#: Architecture_of_the_Recovery_Manager.xml:476
#, no-c-format
+#, fuzzy
msgid ""
"The transaction tables are accessed via the TransactionStatusManager object. "
"On application program initialisation the host/port pair that represents the "
"TransactionStatusManager is written to the Object Store in '../Recovery/"
"TransactionStatusManager’ part of the Object Store file hierarchy and "
"identified by the process Uid of the application process."
-msgstr ""
+msgstr "事务表通过 TransactionStatusManager 对象进行访问。"
#. Tag: para
#: Architecture_of_the_Recovery_Manager.xml:479
@@ -1432,7 +1435,7 @@
#: Architecture_of_the_Recovery_Manager.xml:484
#, no-c-format
msgid "TransactionStatusManager"
-msgstr ""
+msgstr "TransactionStatusManager"
#. Tag: para
#: Architecture_of_the_Recovery_Manager.xml:485
@@ -1446,12 +1449,14 @@
"Any free port is used by the TransactionStatusManager by default, however "
"the port can be fixed with the property:"
msgstr ""
+"这个对象作为切换管理者从运行的 HPTS 应用程序进程获取事务状态的接口。com."
+"arjuna.ats.arjuna.coordinator.InitAction 类为每个应用程序进程都创建一个 TransactionStatusManager。目前 RecoveryManager 和 TransactionStatusManager 之间的通信使用了一个 tcp 连接。TransactionStatusManager 缺省使用任何空闲端口，但你用下面的属性固定端口号："
#. Tag: screen
#: Architecture_of_the_Recovery_Manager.xml:488
#, no-c-format
msgid "com.arjuna.ats.arjuna.recovery.transactionStatusManagerPort"
-msgstr ""
+msgstr "com.arjuna.ats.arjuna.recovery.transactionStatusManagerPort"
#. Tag: para
#: Architecture_of_the_Recovery_Manager.xml:489
@@ -1465,7 +1470,7 @@
"accepts a transaction Uid and a transaction type (if available) from a "
"TransactionStatusConnector, the transaction status is obtained from the "
"local thransaction table and returned back to the TransactionStatusConnector."
-msgstr ""
+msgstr "在创建时，TransactionStatusManager 获取一个端口号并和主机一起作为 TransactionStatusManagerItem 存储到对象库里。Listener 线程被启动，它等待 TransactionStatusConnector 的连接请求。当连接被建立时，Connection 线程将被创建，它运行的服务（AtomicActionStatusService）从 TransactionStatusConnector 接受事务 UID 和事务类型（如果可用），事务状态从本地事务表里获得并返回给 TransactionStatusConnector。"
#. Tag: title
#: Architecture_of_the_Recovery_Manager.xml:494
Modified: labs/jbosstm/enterprise/tags/EAP_4_3_0/Transactions_Failure_Recovery_Guide/zh-CN/How_JBossTS_managers_the_OTS_Recovery_Protocol.po
===================================================================
--- labs/jbosstm/enterprise/tags/EAP_4_3_0/Transactions_Failure_Recovery_Guide/zh-CN/How_JBossTS_managers_the_OTS_Recovery_Protocol.po 2008-11-19 04:51:54 UTC (rev 23938)
+++ labs/jbosstm/enterprise/tags/EAP_4_3_0/Transactions_Failure_Recovery_Guide/zh-CN/How_JBossTS_managers_the_OTS_Recovery_Protocol.po 2008-11-19 04:51:54 UTC (rev 23939)
@@ -8,8 +8,8 @@
"Project-Id-Version: How_JBossTS_managers_the_OTS_Recovery_Protocol\n"
"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
"POT-Creation-Date: 2008-09-23 06:30+0000\n"
-"PO-Revision-Date: 2008-11-18 16:17+1000\n"
-"Last-Translator: Xi HUANG <xhuang at redhat.com>\n"
+"PO-Revision-Date: 2008-11-19 11:57+1000\n"
+"Last-Translator: \n"
"Language-Team: <en at li.org>\n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=UTF-8\n"
@@ -75,7 +75,7 @@
"enhances performance by avoiding the creation of servants but it relies on a "
"default RecoveryCoordinator object with it’s associated default servant to "
"manage all replay_completion invocations."
-msgstr ""
+msgstr "在每个注册的资源上，一个 RecoveryCoordinator 对象将被创建并返回给调用 register_resource 操作的应用程序。在每个 CORBA 对象后面，都应该有一个对象实现或 Servant 对象，按照 POA 的术语，它执行 RecoveryCoordinator 对象上的操作。不是在每个 register_resource 上用相关联的 servant 创建 RecoveryCoordinator 对象，JBossTS 通过避免 servant 的创建来增强性能，但它依赖于缺省的 RecoveryCoordinator 对象和相关联的缺省 servant 来管理所有的 replay_completion 调用。"
#. Tag: para
#: How_JBossTS_managers_the_OTS_Recovery_Protocol.xml:30
@@ -84,7 +84,7 @@
"In the next sections we first give an overview of the Portable Object "
"Adapter architecture, then we describe how this architecture is used to "
"provide RecoveryCoordinator creation with optimization as explained above."
-msgstr ""
+msgstr "在下面的章节里，我们首先给出可移植对象适配器架构的概述，然后我们将讨论这个构架是如何被用来提供优化的 RecoveryCoordinator 创建的。"
#. Tag: title
#: How_JBossTS_managers_the_OTS_Recovery_Protocol.xml:34
@@ -277,7 +277,7 @@
"or the NON_RETAIN policy is set, the request is dispatched to the default "
"servant. If no default servant has been registered, an OBJ_ADAPTER exception "
"is returned. The POA must also use the MULTIPLE_ID policy with this value."
-msgstr ""
+msgstr "USE_DEFAULT_SERVANT：如果对象 ID 没有在活动对象表里列出，或者设置了 NON_RETAIN 策略，请求将被分派给缺省的 servant。如果没有注册缺省的 servant，OBJ_ADAPTER 异常将被返回。对于这个值，POA 必须也使用 MULTIPLE_ID 策略。"
#. Tag: para
#: How_JBossTS_managers_the_OTS_Recovery_Protocol.xml:153
@@ -286,7 +286,7 @@
"USE_SERVANT_MANAGER: If the Object ID is not listed in the Active Object Map "
"or the NON_RETAIN policy is set, the servant manager is used to obtain a "
"servant."
-msgstr ""
+msgstr "USE_SERVANT_MANAGER：如果对象 ID 没有在活动对象表里列出，或者设置了 NON_RETAIN 策略，Servant 管理者将被用来获取 servant。"
#. Tag: para
#: How_JBossTS_managers_the_OTS_Recovery_Protocol.xml:160
@@ -295,7 +295,7 @@
"Implicit Activation policy: Specifies whether the POA supports implicit "
"activation of servants. The Implicit Activation policy can have the "
"following values:"
-msgstr ""
+msgstr "Implicit Activation 策略：指定 POA 是否支持隐性地激活 servant。Implicit Activation 策略可以有下列的值："
#. Tag: para
#: How_JBossTS_managers_the_OTS_Recovery_Protocol.xml:165
@@ -306,7 +306,7 @@
"<methodname>org.omg.PortableServer.POA.servant_to_reference()</methodname> "
"or by invoking <methodname>_this()</methodname> on the servant. The POA must "
"also use the SYSTEM_ID and RETAIN policies with this value."
-msgstr ""
+msgstr "IMPLICIT_ACTIVATION：POA 支持 servant 的隐性激活。Servant 可以通过转换为带有 <methodname>org.omg.PortableServer.POA.servant_to_reference()</methodname> 的对象引用或调用 <methodname>_this()</methodname> 来激活。对于这个值，POA 也必须使用 SYSTEM_ID 和 RETAIN 策略。"
#. Tag: para
#: How_JBossTS_managers_the_OTS_Recovery_Protocol.xml:170
@@ -314,7 +314,7 @@
msgid ""
"NO_IMPLICIT_ACTIVATION (Default): The POA does not support implicit "
"activation of servants."
-msgstr ""
+msgstr "NO_IMPLICIT_ACTIVATION（缺省）：POA 不支持 servant 的隐性激活。"
#. Tag: para
#: How_JBossTS_managers_the_OTS_Recovery_Protocol.xml:177
@@ -333,13 +333,13 @@
"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."
-msgstr ""
+msgstr "把 replay_completion 调用重定向到缺省的 servant，我们需要创建使用分配了 USE_DEFAULT_SERVANT 值的 Request Processing 策略的 POA。然而，为了到达到达缺省的 Servant，我们首先应该到达转发请求给缺省 servant 的 POA。实际上，ORB 使用一系列信息来获取 POA；这些信息包含在客户端使用的对象引用里。在这些信息中，有服务器的 IP 地址和端口号以及 POA 名称。JBossTS 为每台主机提供一个 servant 来执行 replay_completion 调用。这个 servant 位于 RecoveryManager 进程里。RecoveryManager 进程是独立于客户端和服务器应用程序的进程。下节解释了如何为 ORBIX 和 JacORB 提供位于独立进程里的缺省 servant 的间接定位。"
#. Tag: title
#: How_JBossTS_managers_the_OTS_Recovery_Protocol.xml:182
#, no-c-format
msgid "The default RecoveryCoordinator in Orbix"
-msgstr ""
+msgstr "Orbix 里的缺省 RecoveryCoordinator"
#. Tag: para
#: How_JBossTS_managers_the_OTS_Recovery_Protocol.xml:183
@@ -356,7 +356,7 @@
"address that it should use. This is done by creating a "
"<code>WellKnownAddressingPolicy</code> object and setting its value to the "
"configuration scope that contains the well-known address."
-msgstr ""
+msgstr "在 Orbix 里，对象通过 Location 守护进程来定位。为了避免超载使用 Location 守护进程，Orbix 提供了一个名为 <emphasis>Direct Persistence</emphasis> 的机制，允许生成持久性的对象引用。这个机制实际上是一个私有策略 DIRECT_PERSISTENCE。使用 PERSISTENT 和 DIRECT_PERSISTENCE 策略的 POA 生成包含服务器进程的知名地址的 IOR。使用直接持久化的 POA 也必须告诉每个传输机制（如 IIOP）在配置文件的哪个部分可以找到它应该使用的知名地址。这是通过创建 <code>WellKnownAddressingPolicy</code> 对象并将其值设置为包含知名地址的配置作用域来实现的。"
#. Tag: para
#: How_JBossTS_managers_the_OTS_Recovery_Protocol.xml:186
@@ -367,7 +367,7 @@
"names. The following configuration modifications are necessary to define the "
"well-know address of the RecoveryCoordinator performing replay_completion "
"invocation."
-msgstr ""
+msgstr "要指定 <code>WellKnownAddressingPolicy</code> 对象使用的地址，JBossTS 使用允许指定 ORB/POA 名称的 Orbix 机制。要定义执行 replay_completion 调用的 RecoveryCoordinator 的知名地址，下列的配置修改是必需的。"
#. Tag: para
#: How_JBossTS_managers_the_OTS_Recovery_Protocol.xml:190
@@ -375,7 +375,7 @@
msgid ""
"Note that this configuration is also necessary to support transaction "
"context propagation and interposition."
-msgstr ""
+msgstr "请注意这个配置也是支持事务上下文传递和插入（interposition）所必需的。"
#. Tag: para
#: How_JBossTS_managers_the_OTS_Recovery_Protocol.xml:194
@@ -384,6 +384,8 @@
"A new orb name domain called arjuna should be created within the main Orbix "
"2000 domain being used by the application. It requires the following format:"
msgstr ""
+"新的 ORB 域名 arjuna 应该在应用程序使用的主要的 Orbix "
+"2000 域里创建。它要求下面的格式："
#. Tag: screen
#: How_JBossTS_managers_the_OTS_Recovery_Protocol.xml:197
@@ -427,6 +429,43 @@
" };\n"
"};"
msgstr ""
+"arjuna\n"
+"{\n"
+" portable_interceptor\n"
+" {\n"
+" orb_plugins = [\"local_log_stream\", \"iiop_profile\", \"giop"
+"\", \"iiop\", \"portable_interceptor\"];\n"
+" \n"
+" ots_recovery_coordinator\n"
+" {\n"
+" recovery_coordinator:iiop:addr_list = [“<name>:"
+"<port>”];\n"
+" };\n"
+" \n"
+" ots_transaction\n"
+" {\n"
+" transaction:iiop:addr_list = [“+<name>:<"
+"port>”];\n"
+" }; \n"
+" ots_context\n"
+" {\n"
+" binding:client_binding_list = [\"OTS_Context\", "
+"\"OTS_Context+GIOP+SIOP\", \"GIOP+SIOP\", \"OTS_Context+GIOP+IIOP\", \"GIOP"
+"+IIOP\"];\n"
+" binding:server_binding_list = [\"OTS_Context\", "
+"\"\"];\n"
+" };\n"
+" \n"
+" ots_interposition\n"
+" {\n"
+" binding:client_binding_list = [\"OTS_Interposition"
+"\", \"OTS_Interposition+GIOP+SIOP\", \"GIOP+SIOP\", \"OTS_Interposition+GIOP"
+"+IIOP\", \"GIOP+IIOP\"];\n"
+" binding:server_binding_list = [\"OTS_Interposition"
+"\", \"\"];\n"
+" };\n"
+" };\n"
+"};"
#. Tag: para
#: How_JBossTS_managers_the_OTS_Recovery_Protocol.xml:198
@@ -435,7 +474,7 @@
"The <name> field should be substituted by the name of the machine on "
"which JBossTS is being run. The <port> field should be an unused port "
"on which the JBossTS recovery manager may listen for recovery requests."
-msgstr ""
+msgstr "<name> 字段应该用运行 JBossTS 的机器名代替。<port> 字段应该为 BossTS 切换管理者侦听切换请求的空闲端口。"
#. Tag: para
#: How_JBossTS_managers_the_OTS_Recovery_Protocol.xml:201
@@ -450,19 +489,23 @@
"interposition, the <parameter>–ORBname.arjuna.portable_interceptor."
"ots_interposition</parameter> parameter should be used. For example:"
msgstr ""
+"因为 Orbix 和持久性 POA 协同工作的模式，如果你想对应用程序应用失效切换，在运行客户端和服务时，你必须使用 Arjuna "
+"ORB 名称中的一个（propagation 或 interposition）。当只使用事务上下文传递（propagation）时，<parameter>–"
+"ORBname arjuna.portable_interceptor.ots_context</parameter> 参数应该传递给客户端和服务器。当既使用 propagation 又使用 interposition 时，<parameter>–ORBname.arjuna.portable_interceptor."
+"ots_interposition</parameter> 参数应该被使用。例如："
#. Tag: screen
#: How_JBossTS_managers_the_OTS_Recovery_Protocol.xml:204
#, no-c-format
msgid "java mytest –ORBname arjuna.portable_interceptor.ots_context"
-msgstr ""
+msgstr "java mytest –ORBname arjuna.portable_interceptor.ots_context"
#. Tag: title
#: How_JBossTS_managers_the_OTS_Recovery_Protocol.xml:206
#: How_JBossTS_managers_the_OTS_Recovery_Protocol.xml:287
#, no-c-format
msgid "How it works"
-msgstr ""
+msgstr "它是如何工作的"
#. Tag: para
#: How_JBossTS_managers_the_OTS_Recovery_Protocol.xml:207
@@ -480,6 +523,8 @@
"<interfacename>RecoveryActivator</interfacename> that leads to the creation "
"of the default servant that performs all replay_invocations requests."
msgstr ""
+"当切换管理者被启动时，它在配置文件里搜索需要加载的 RecoveryActivator。一旦完成，它调用每个加载进程的 <methodname>startRCservice</methodname> 方法。如前面章节（切换管理者）里所述，加载类是实现了 <interfacename>RecoveryActivator</interfacename> 接口的 <classname>RecoveryEnablement</classname>。这个位于 <package>com.arjuna.ats.internal.jts.orbspecific."
+"recovery</package> 包里的通用类，隐藏了应用程序（JacORB）所使用的 ORB 的性质。下图解释了 <interfacename>RecoveryActivator</interfacename> 的行为，它创建执行 replay_completion 调用的缺省 servant。"
#. Tag: caption
#: How_JBossTS_managers_the_OTS_Recovery_Protocol.xml:215
@@ -487,7 +532,7 @@
msgid ""
"The Recovery Manager and the creation of the default servant for "
"RecoveryCoordinator."
-msgstr ""
+msgstr "切换管理者和用于 RecoveryCoordinator 的缺省 servant 的创建。"
#. Tag: para
#: How_JBossTS_managers_the_OTS_Recovery_Protocol.xml:218
@@ -496,7 +541,7 @@
"There is one recovery Manager Process per machine, then one default servant "
"per machine. Performing all replay_completion invocations means those made "
"on the same machine."
-msgstr ""
+msgstr "每台主机有一个切换管理者进程以及一个缺省的 servant。执行所有的 replay_completion 调用仅表示相同主机上的所有的调用。"
#. Tag: para
#: How_JBossTS_managers_the_OTS_Recovery_Protocol.xml:222
@@ -509,7 +554,7 @@
"register_resource invocations, as illustrated in figure below. The Object "
"reference created has an Object ID that contains the transaction ID in "
"progress and the Process Identifier of the application."
-msgstr ""
+msgstr "当启动时，以 library 模式使用 JBossTS 的应用程序将被启动，子 POA 用切换管理者里定义的相同策略创建。这个子 POA 被用来创建 RecoveryCoordinator CORBA 的对象引用，如下图所述，它需要在调用 register_resource 时返回。被创建的对象引用有一个包含事务 ID 和应用程序进程 ID 的对象 ID。"
#. Tag: para
#: How_JBossTS_managers_the_OTS_Recovery_Protocol.xml:226
@@ -518,13 +563,13 @@
"If the Transaction Service is used in the stand-alone mode, the behavior to "
"create object reference to RecoveryCoordinator objects is exactly the same; "
"the process ID used in the Object ID is the Transaction Service process ID"
-msgstr ""
+msgstr "如果事务服务以独立模式使用，创建 RecoveryCoordinator 对象的引用的行为刚好相同；对象 ID 里使用的进程 ID 就是事务服务的进程 ID。"
#. Tag: caption
#: How_JBossTS_managers_the_OTS_Recovery_Protocol.xml:234
#, no-c-format
msgid "Resource registration and returned RecoveryCoordinator Object reference."
-msgstr ""
+msgstr "资源注册和返回的 RecoveryCoordinator 对象引用。"
#. Tag: para
#: How_JBossTS_managers_the_OTS_Recovery_Protocol.xml:236
@@ -536,19 +581,19 @@
"is assigned to the POA included in the object reference, the request is "
"forward straight to the default servant defined in the Recovery Manager, as "
"described in the figure below."
-msgstr ""
+msgstr "有了 RecoveryCoordinator 的对象引用，应用程序可以用它来检测创建该对象引用的事务的状态。如下图所述，当 RecoveryCoordinator 按照 POA 策略被分配给对象引用里包括的 POA 时，请求将被直接转发给切换管理者里定义的缺省 servant。"
#. Tag: caption
#: How_JBossTS_managers_the_OTS_Recovery_Protocol.xml:243
#, no-c-format
msgid "replay_completion invocation forwarded to the default RecoveryCoordinator ."
-msgstr ""
+msgstr "转发到缺省 RecoveryCoordinator 的 replay_completion 调用。"
#. Tag: para
#: How_JBossTS_managers_the_OTS_Recovery_Protocol.xml:245
#, no-c-format
msgid "The flow described in the figure can be depicted as follow:"
-msgstr ""
+msgstr "图例里的流程可以这样描述："
#. Tag: para
#: How_JBossTS_managers_the_OTS_Recovery_Protocol.xml:250
@@ -557,7 +602,7 @@
"The participant invokes the replay_completion operation on "
"RecoveryCoordinator object using the object reference returned by the "
"Transaction Server."
-msgstr ""
+msgstr "参与者通过事务服务器返回的对象引用调用 RecoveryCoordinator 对象的 replay_completion 操作。"
#. Tag: para
#: How_JBossTS_managers_the_OTS_Recovery_Protocol.xml:255
@@ -566,12 +611,14 @@
"The request is forwarded to the Recovery Manager process since the Well-"
"known-address policy is used to retrieve."
msgstr ""
+"既然使用了 Well-"
+"known-address 策略，请求被转发给切换管理者进程。"
#. Tag: para
#: How_JBossTS_managers_the_OTS_Recovery_Protocol.xml:260
#, no-c-format
msgid "The child POA responsible to locate the servant is retrieved."
-msgstr ""
+msgstr "子 POA 负责定位被获取的 servant。"
#. Tag: para
#: How_JBossTS_managers_the_OTS_Recovery_Protocol.xml:265
@@ -580,7 +627,7 @@
"After looking to the Active Object Map, the child POA invokes the default "
"servant to perform the request. Note that the Object ID conveyed by the "
"object reference is not retrieved in the AOP."
-msgstr ""
+msgstr "在查看活动对象表之后，子 POA 调用缺省的 servant 来处理请求。请注意，对象引用传递的对象 ID 不在 AOP 里获取。"
#. Tag: para
#: How_JBossTS_managers_the_OTS_Recovery_Protocol.xml:270
@@ -590,7 +637,7 @@
"Transaction ID and the process ID of the Transaction Server process. To "
"determine if the process still alive, the TransactionStatusConnectionManager "
"functionalities are used."
-msgstr ""
+msgstr "servant 从请求里抽取包含事务 ID 和事务服务器进程的进程 ID 的对象 ID。为了获知进程是否仍然活动，TransactionStatusConnectionManager 功能会被使用。"
#. Tag: para
#: How_JBossTS_managers_the_OTS_Recovery_Protocol.xml:275
@@ -599,7 +646,7 @@
"According to the presence or not of the Transaction Server process and "
"eventually the returned status, the servant returns the status of the "
"transaction asked by the participant."
-msgstr ""
+msgstr "按照事务服务器进程的有无以及最终所返回的状态，servant 返回参与者请求的事务的状态。"
#. Tag: title
#: How_JBossTS_managers_the_OTS_Recovery_Protocol.xml:282
@@ -636,7 +683,7 @@
"<interfacename>RecoveryActivator</interfacename> that leads to the creation "
"of the default servant that performs replay_completion invocations requests."
msgstr ""
-"当切换管理者被启动时，它搜索需要加载的 RecoveryActivator 的配置。一旦完成，它调用每个加载进程的 <methodname>startRCservice</methodname> 方法。如前面章节（切换管理者）里所述，加载类是实现了 <interfacename>RecoveryActivator</interfacename> 接口的 <classname>RecoveryEnablement</classname>。这个位于 <package>com.arjuna.ats.internal.jts.orbspecific."
+"当切换管理者被启动时，它在配置文件里搜索需要加载的 RecoveryActivator。一旦完成，它调用每个加载进程的 <methodname>startRCservice</methodname> 方法。如前面章节（切换管理者）里所述，加载类是实现了 <interfacename>RecoveryActivator</interfacename> 接口的 <classname>RecoveryEnablement</classname>。这个位于 <package>com.arjuna.ats.internal.jts.orbspecific."
"recovery</package> 包里的通用类，隐藏了应用程序（JacORB）所使用的 ORB 的性质。下图解释了 <interfacename>RecoveryActivator</interfacename> 的行为，它创建执行 replay_completion 调用的缺省 servant。"
#. Tag: para
@@ -671,7 +718,7 @@
"ID of the transaction in progress and also the Process ID of the process "
"that is creating the new <code>RecoveryCoordinator</code> object reference, "
"as illustrated below."
-msgstr ""
+msgstr "当应用程序在事务里注册资源时，<code>RecoveryCoordinator</code> 对象引用将被返回。要构建这个对象引用，事务服务（Transaction Service）把资源管理者里创建的 RecoveryCoordinator 对象引用作为模板使用。新的对象引用包含和获取缺省 servant 几乎相同的信息（IP 地址、端口号、POA 名称等），但对象 ID 改变了。如下所述，它包含运行的事务的 ID 以及创建新的 <code>RecoveryCoordinator</code> 对象引用的进程的 ID。"
#. Tag: caption
#: How_JBossTS_managers_the_OTS_Recovery_Protocol.xml:308
@@ -679,7 +726,7 @@
msgid ""
"Resource registration and returned RecoveryCoordinator Object reference "
"build from a reference stored in the ObjectStore."
-msgstr ""
+msgstr "资源注册和所返回的从对象库存储的引用构建的 RecoveryCoordinator 对象引用。"
#. Tag: para
#: How_JBossTS_managers_the_OTS_Recovery_Protocol.xml:310
@@ -693,4 +740,6 @@
"extract the transaction identifier and the process identifier needed to "
"determine the status of the requested transaction."
msgstr ""
+"既然返回给应用程序的 <code>RecoveryCoordintaor</code> 对象引用包含所有用于获取 POA 的信息，那么位于资源管理者里的缺省 servant、所有的 replay_completion 调用都会被转发给相同的缺省 <code>RecoveryCoordinator</"
+"code>，它能够从转入请求里获取对象 ID 来抽取决定被请求事务的状态的事务标识符和进程标识符。"
More information about the jboss-svn-commits
mailing list