[jboss-svn-commits] JBL Code SVN: r23818 - 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 11 02:01:15 EST 2008
Author: xhuang at jboss.com
Date: 2008-11-11 02:01:15 -0500 (Tue, 11 Nov 2008)
New Revision: 23818
Modified:
labs/jbosstm/enterprise/tags/EAP_4_3_0/Transactions_Failure_Recovery_Guide/zh-CN/Architecture_of_the_Recovery_Manager.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-11 05:53:15 UTC (rev 23817)
+++ labs/jbosstm/enterprise/tags/EAP_4_3_0/Transactions_Failure_Recovery_Guide/zh-CN/Architecture_of_the_Recovery_Manager.po 2008-11-11 07:01:15 UTC (rev 23818)
@@ -1,3 +1,4 @@
+# translation of Architecture_of_the_Recovery_Manager.po to
# Language zh-CN translations for package.
# Automatically generated, 2008.
#
@@ -3,25 +4,26 @@
msgid ""
msgstr ""
-"Project-Id-Version: \n"
+"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-09-23 06:30+0000\n"
-"Last-Translator: Automatically generated\n"
-"Language-Team: none\n"
+"PO-Revision-Date: 2008-11-11 20:00+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"
"Content-Transfer-Encoding: 8bit\n"
+"X-Generator: KBabel 1.11.4\n"
#. Tag: title
#: Architecture_of_the_Recovery_Manager.xml:6
#, no-c-format
msgid "Architecture of the Recovery Manager"
-msgstr ""
+msgstr "切换管理者的架构"
#. Tag: title
#: Architecture_of_the_Recovery_Manager.xml:8
#, no-c-format
msgid "Crash Recovery Overview"
-msgstr ""
+msgstr "崩溃恢复概述"
#. Tag: para
@@ -31,7 +33,7 @@
msgid ""
"The main architectural components within Crash Recovery are illustrated in "
"the diagram below:"
-msgstr ""
+msgstr "下图演示了崩溃恢复的主要构架性组件："
#. Tag: para
#: Architecture_of_the_Recovery_Manager.xml:17
@@ -44,13 +46,13 @@
"the commit phase to the Object Store. On successfully committing a "
"transaction this data is removed, however if the transaction fails then this "
"data remains within the Object Store."
-msgstr ""
+msgstr "恢复管理者（Recovery Manager）是负责执行崩溃恢复的守护进程。每个节点只运行一个恢复管理者。对象库为事务提供持久性数据存储在记录日志。在普通的事务处理过程中，每个事务将把提交阶段的日志登记到对象库里。成功提及事务后，这个数据将被删除，然而如果事务提及失败，这个数据将保留在对象库里。"
#. Tag: para
#: Architecture_of_the_Recovery_Manager.xml:20
#, no-c-format
msgid "The Recovery Manager functions by:"
-msgstr ""
+msgstr "恢复管理者的功能有："
#. Tag: para
#: Architecture_of_the_Recovery_Manager.xml:25
@@ -60,7 +62,7 @@
"failed. Failed transactions are indicated by the presence of log data after "
"a period of time that the transaction would have normally been expected to "
"finish."
-msgstr ""
+msgstr "定期地扫描对象库里可能失败的事务。事务通常会在一段时间内完成，之后存在的日志数据表示这个事务失败了。"
#. Tag: para
#: Architecture_of_the_Recovery_Manager.xml:30
@@ -68,7 +70,7 @@
msgid ""
"Checking with the application process which originated the transaction "
"whether the transaction is still in progress or not."
-msgstr ""
+msgstr "通过发起事务的应用程序过程检查事务是否仍在进行。"
#. Tag: para
#: Architecture_of_the_Recovery_Manager.xml:35
@@ -76,20 +78,19 @@
msgid ""
"Recovering the transaction by re-activating the transaction and then "
"replaying phase two of the commit protocol."
-msgstr ""
+msgstr "通过重新激活事务并重启两阶段提交协议来恢复事务。"
#. Tag: para
#: Architecture_of_the_Recovery_Manager.xml:40
#, no-c-format
-msgid ""
-"The following sections describe the architectural components in more detail"
-msgstr ""
+msgid "The following sections describe the architectural components in more detail"
+msgstr "下面的章节描述了构架性组件的更多细节。"
#. Tag: title
#: Architecture_of_the_Recovery_Manager.xml:46
#, no-c-format
msgid "Recovery Manager"
-msgstr ""
+msgstr "恢复管理者"
#. Tag: para
#: Architecture_of_the_Recovery_Manager.xml:47
@@ -98,7 +99,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."
-msgstr ""
+msgstr "初始化时，恢复管理者首先加载属性文件里的配置信息。这个配置信息包括了大量的恢复 activator 和恢复模块，它们都是动态加载的。"
#. Tag: para
#: Architecture_of_the_Recovery_Manager.xml:50
@@ -114,7 +115,7 @@
"<interfacename>RecoveryActivitor</interfacename> has the responsibility to "
"create a RecoveryCoordinator object able to respond to the replay_completion "
"operation."
-msgstr ""
+msgstr "从 JBossTS 3.0 开始，恢复管理者不捆绑专门的 Object Request Broker（ORB）。因此，OTS 恢复协议没有隐性地启用。要启用这个协议，我们使用恢复催化剂（recovery activator）的概念，它用初始化一个和底层通信协议相关的 recovery 类的 <interfacename>RecoveryActivator</interfacename> 接口定义。例如，当和 OTS 一起使用时，<interfacename>RecoveryActivitor</interfacename> 负责创建能够响应 replay_completion 操作的 RecoveryCoordinator 对象。"
#. Tag: para
#: Architecture_of_the_Recovery_Manager.xml:53
@@ -123,7 +124,7 @@
"All <interfacename>RecoveryActivator</interfacename> instances inherit the "
"same interface. They are loaded via the following recovery extension "
"property:"
-msgstr ""
+msgstr "所有的 <interfacename>RecoveryActivator</interfacename> 实例都继承了相同的接口。它们通过下列的恢复扩展属性进行加载："
#. Tag: screen
#: Architecture_of_the_Recovery_Manager.xml:56
@@ -133,6 +134,9 @@
" name=\"com.arjuna.ats.arjuna.recovery."
"recoveryActivator_<number>\" value=\"RecoveryClass\" />"
msgstr ""
+"<property \n"
+" name=\"com.arjuna.ats.arjuna.recovery."
+"recoveryActivator_<number>\" value=\"RecoveryClass\" />"
#. Tag: para
#: Architecture_of_the_Recovery_Manager.xml:57
@@ -140,7 +144,7 @@
msgid ""
"For instance the <interfacename>RecoveryActivator</interfacename> provided "
"in the distribution of JTS/OTS, which shall not be commented, is as follow:"
-msgstr ""
+msgstr "JTS/OTS 里提供的 <interfacename>RecoveryActivator</interfacename> 不应该被注释，如下所示："
#. Tag: screen
#: Architecture_of_the_Recovery_Manager.xml:60
@@ -150,6 +154,9 @@
" name=\"com.arjuna.ats.arjuna.recovery.recoveryActivator_1\" value="
"\"com.arjuna.ats.internal.jts.orbspecific.recovery.RecoveryEnablement/>"
msgstr ""
+"<property \n"
+" name=\"com.arjuna.ats.arjuna.recovery.recoveryActivator_1\" value="
+"\"com.arjuna.ats.internal.jts.orbspecific.recovery.RecoveryEnablement/>"
#. Tag: para
#: Architecture_of_the_Recovery_Manager.xml:61
@@ -168,7 +175,7 @@
msgid ""
"Each recovery module is used to recover a different type of transaction/"
"resource, however each recovery module inherits the same basic behavior."
-msgstr ""
+msgstr "每个恢复模块都被用来恢复不同类型的事务/资源，然而每个恢复模块都继承了相同的基本行为。"
#. Tag: para
#: Architecture_of_the_Recovery_Manager.xml:67
@@ -181,7 +188,7 @@
"backoff period. The timeout between the end of the second pass and the start "
"of the first pass is the recovery period. The recovery period is larger than "
"the backoff period."
-msgstr ""
+msgstr "恢复由两个独立的过程/阶段组成，它们由两个超时时期进分隔。第一个阶段检查对象库里可能失败的事务；第二个阶段对这些事务执行崩溃恢复。两个阶段之间的时间间隔称为 backoff 周期。第二个阶段结束和第一个阶段开始之间的时间称为恢复周期（Recovery period）。恢复周期比 backoff 周期要长。"
#. Tag: para
#: Architecture_of_the_Recovery_Manager.xml:70
@@ -191,7 +198,7 @@
"applies the backoff period timeout, invokes the second pass upon each "
"recovery module and finally applies the recovery period timeout before "
"restarting the first pass again."
-msgstr ""
+msgstr "恢复管理者对每一个恢复模块调用第一个过程，应用 backoff 周期并为每个恢复模块调用第二个过程，最后在重启第一个过程之前应用恢复周期。"
#. Tag: para
#: Architecture_of_the_Recovery_Manager.xml:73
@@ -199,7 +206,7 @@
msgid ""
"The recovery modules are loaded via the following recovery extension "
"property:"
-msgstr ""
+msgstr "恢复模块通过下列的恢复扩展属性进行加载："
#. Tag: screen
#: Architecture_of_the_Recovery_Manager.xml:76
@@ -208,6 +215,8 @@
"com.arjuna.ats.arjuna.recovery.recoveryExtension<number>=<"
"RecoveryClass>"
msgstr ""
+"com.arjuna.ats.arjuna.recovery.recoveryExtension<number>=<"
+"RecoveryClass>"
#. Tag: para
#: Architecture_of_the_Recovery_Manager.xml:77
@@ -215,7 +224,7 @@
msgid ""
"The backoff period and recovery period are set using the following "
"properties:"
-msgstr ""
+msgstr "Backoff 周期和恢复周期用下列属性进行设置："
#. Tag: screen
#: Architecture_of_the_Recovery_Manager.xml:80
@@ -226,18 +235,22 @@
"com.arjuna.ats.arjuna.recovery.periodicRecovery (default 120 "
"secs)"
msgstr ""
+"com.arjuna.ats.arjuna.recovery.recoveryBackoffPeriod (缺省为 10 "
+"秒)\n"
+"com.arjuna.ats.arjuna.recovery.periodicRecovery (缺省为 120 "
+"秒)"
#. Tag: para
#: Architecture_of_the_Recovery_Manager.xml:81
#, no-c-format
msgid "The following java classes are used to implement the Recovery Manager:"
-msgstr ""
+msgstr "下列的 Java 类被用来实现恢复管理者："
#. Tag: para
#: Architecture_of_the_Recovery_Manager.xml:86
#, no-c-format
msgid "package <package>com.arjuna.ats.arjuna.recovery</package>:"
-msgstr ""
+msgstr "<package>com.arjuna.ats.arjuna.recovery</package> 包："
#. Tag: para
#: Architecture_of_the_Recovery_Manager.xml:91
@@ -245,13 +258,13 @@
msgid ""
"RecoveryManager: The daemon process that starts up by instantiating an "
"instance of the RecoveryManagerImple class."
-msgstr ""
+msgstr "RecoveryManager：通过实例化 RecoveryManagerImple 的一个实例来启动的守护进程。"
#. Tag: para
#: Architecture_of_the_Recovery_Manager.xml:96
#, no-c-format
msgid "RecoveryEnvironment: Properties used by the recovery manager."
-msgstr ""
+msgstr "RecoveryEnvironment：恢复管理者使用的属性。"
#. Tag: para
#: Architecture_of_the_Recovery_Manager.xml:101
@@ -259,13 +272,13 @@
msgid ""
"RecoveryConfiguration: Specifies the name of the Recovery Manager property "
"file. (for instance, RecoveryManager-properties.xml)"
-msgstr ""
+msgstr "RecoveryConfiguration：指定恢复管理者属性文件的名称（例如，RecoveryManager-properties.xml）。"
#. Tag: para
#: Architecture_of_the_Recovery_Manager.xml:108
#, no-c-format
msgid "package <package>com.arjuna.ats.internal.ts.arjuna.recovery</package>:"
-msgstr ""
+msgstr "<package>com.arjuna.ats.internal.ts.arjuna.recovery</package> 包："
#. Tag: para
#: Architecture_of_the_Recovery_Manager.xml:113
@@ -274,7 +287,7 @@
"RecoveryManagerImple: Creates and starts instances of the "
"RecActivatorLoader, the PeriodicRecovery thread and the ExpiryEntryMonitor "
"thread."
-msgstr ""
+msgstr "RecoveryManagerImple：创建和启动 RecActivatorLoader 实例、PeriodicRecovery 线程和 ExpiryEntryMonitor 线程。"
#. Tag: para
#: Architecture_of_the_Recovery_Manager.xml:118
@@ -283,7 +296,7 @@
"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."
-msgstr ""
+msgstr "RecActivatorLoader：动态地加载属性文件里指定的 RecoveryActivator。每个 RecoveryActicator 都被指定为属性文件里的恢复扩展选项。"
#. Tag: para
#: Architecture_of_the_Recovery_Manager.xml:123
@@ -293,7 +306,7 @@
"first pass method for each module, applies the backoff period timeout, calls "
"the second pass method for each module and applies the recovery period "
"timeout."
-msgstr ""
+msgstr "PeriodicRecovery：加载每个恢复模块、并为每个模块调用第一个过程的线程，应用 backoff 周期，为每个模块用第二个过并应用恢复周期。"
#. Tag: para
#: Architecture_of_the_Recovery_Manager.xml:128
@@ -319,7 +332,7 @@
#: Architecture_of_the_Recovery_Manager.xml:141
#, no-c-format
msgid "Embedding the Recovery Manager"
-msgstr ""
+msgstr "嵌入恢复管理者"
#. Tag: para
#: Architecture_of_the_Recovery_Manager.xml:142
@@ -514,8 +527,7 @@
#. Tag: title
#: Architecture_of_the_Recovery_Manager.xml:225
#, no-c-format
-msgid ""
-"com.arjuna.ats.internal.jts.recovery.transactions.TransactionRecoveryModule"
+msgid "com.arjuna.ats.internal.jts.recovery.transactions.TransactionRecoveryModule"
msgstr ""
#. Tag: para
@@ -617,13 +629,13 @@
#: Architecture_of_the_Recovery_Manager.xml:263
#, no-c-format
msgid "Transactional Object pseudo code"
-msgstr ""
+msgstr "Transactional Object 伪代码"
#. Tag: para
#: Architecture_of_the_Recovery_Manager.xml:264
#, no-c-format
msgid "First Pass"
-msgstr ""
+msgstr "第一阶段"
#. Tag: screen
#: Architecture_of_the_Recovery_Manager.xml:266
@@ -1459,7 +1471,7 @@
#: Architecture_of_the_Recovery_Manager.xml:494
#, no-c-format
msgid "Object Store"
-msgstr ""
+msgstr "对象库"
#. Tag: para
#: Architecture_of_the_Recovery_Manager.xml:495
@@ -1469,6 +1481,8 @@
"inheritance. Thus AtomicAction transactions are stored in file path ../"
"StateManager/BasicAction/AtomicAction."
msgstr ""
+"所有的对象都以类名相等的文件名存储。因此 AtomicAction 事务存储为 ../"
+"StateManager/BasicAction/AtomicAction。"
#. Tag: para
#: Architecture_of_the_Recovery_Manager.xml:498
@@ -1478,4 +1492,5 @@
"which is a process id in which the object was created. The Recovery Manager "
"uses the process id to locate transaction status manager items when "
"contacting the originator application process for the transaction status."
-msgstr ""
+msgstr "所有的对象都以唯一的标识符 UID 进行标识。其中一个是创建对象的进程号。当联系事务的发起者程序进程时，恢复管理者使用进程号来定位事务状态管理者条目。"
+
More information about the jboss-svn-commits
mailing list