[jboss-cvs] JBossAS SVN: r74951 - projects/docs/enterprise/4.3/Transactions/Administrators_Guide/zh-CN.
jboss-cvs-commits at lists.jboss.org
jboss-cvs-commits at lists.jboss.org
Tue Jun 24 00:08:04 EDT 2008
Author: xhuang at jboss.com
Date: 2008-06-24 00:08:04 -0400 (Tue, 24 Jun 2008)
New Revision: 74951
Modified:
projects/docs/enterprise/4.3/Transactions/Administrators_Guide/zh-CN/Appendix.po
projects/docs/enterprise/4.3/Transactions/Administrators_Guide/zh-CN/Chapter.po
projects/docs/enterprise/4.3/Transactions/Administrators_Guide/zh-CN/Feedback.po
projects/docs/enterprise/4.3/Transactions/Administrators_Guide/zh-CN/Revision_History.po
Log:
update
Modified: projects/docs/enterprise/4.3/Transactions/Administrators_Guide/zh-CN/Appendix.po
===================================================================
--- projects/docs/enterprise/4.3/Transactions/Administrators_Guide/zh-CN/Appendix.po 2008-06-24 04:07:59 UTC (rev 74950)
+++ projects/docs/enterprise/4.3/Transactions/Administrators_Guide/zh-CN/Appendix.po 2008-06-24 04:08:04 UTC (rev 74951)
@@ -8,7 +8,7 @@
"Project-Id-Version: Appendix\n"
"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
"POT-Creation-Date: 2008-06-19 00:36+0000\n"
-"PO-Revision-Date: 2008-06-16 10:36+1000\n"
+"PO-Revision-Date: 2008-06-24 11:47+1000\n"
"Last-Translator: Xi HUANG <xhuang at redhat.com>\n"
"Language-Team: <en at li.org>\n"
"MIME-Version: 1.0\n"
@@ -26,4 +26,5 @@
#: Appendix.xml:10
#, no-c-format
msgid "<para>TBD</para>"
-msgstr ""
+msgstr "<para>TBD</para>"
+
Modified: projects/docs/enterprise/4.3/Transactions/Administrators_Guide/zh-CN/Chapter.po
===================================================================
--- projects/docs/enterprise/4.3/Transactions/Administrators_Guide/zh-CN/Chapter.po 2008-06-24 04:07:59 UTC (rev 74950)
+++ projects/docs/enterprise/4.3/Transactions/Administrators_Guide/zh-CN/Chapter.po 2008-06-24 04:08:04 UTC (rev 74951)
@@ -8,13 +8,13 @@
"Project-Id-Version: Chapter\n"
"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
"POT-Creation-Date: 2008-06-19 00:36+0000\n"
-"PO-Revision-Date: 2008-06-23 23:02+1000\n"
+"PO-Revision-Date: 2008-06-24 14:07+1000\n"
"Last-Translator: Xi HUANG <xhuang at redhat.com>\n"
-"Language-Team: Chinese Simplified <kde-i18n-doc at lists.kde.org>\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: KAider 0.1\n"
+"X-Generator: KBabel 1.11.4\n"
"Plural-Forms: nplurals=2; plural=n != 1;\n"
#. Tag: title
@@ -91,8 +91,7 @@
#. Tag: para
#: Chapter.xml:19
#, no-c-format
-msgid ""
-"Object store management is critically important to the transaction service."
+msgid "Object store management is critically important to the transaction service."
msgstr "对于事务服务来说，Object store 的管理至关重要。"
#. Tag: title
@@ -103,7 +102,7 @@
#. Tag: para
#: Chapter.xml:25
-#, fuzzy, no-c-format
+#, no-c-format
msgid ""
"Within the transaction service installation, the object store is updated "
"regularly whenever transactions are created, or when Transactional Objects "
@@ -120,7 +119,7 @@
msgstr ""
"在事务访问安装里，只要有事务被创建或是用于 Java 的 Transactional Object 被使用，object store "
"就会被更新。在无故障的环境里，唯一应该驻留在 object store 里的对象状态时那些代表用 Java API "
-"然而，如果发生了故障，事务日志可能保留在 object store 里，直到故障恢复机制已经恢复了它们所代表的事务。因此，"
+"然而，如果发生了故障，事务日志可能保留在 object store 里，直到故障恢复机制已经恢复了它们所代表的事务。因此，删除 object store 的内容需要很小心和谨慎，这很重要，因为这会导致无法解决可疑的事务。此外，如果多个用户共享相同的 object store，他们也需明白这一点。他们不能假定 object store 里的内容是独占资源而简单地进行删除。"
#. Tag: title
#: Chapter.xml:28
@@ -321,6 +320,9 @@
"Commons Logging framework and configuration is assumed to occur through that "
"framework."
msgstr ""
+"很可能安装将希望从 RecoveryManager 里获得某种形式的输出来提供发生恢复的记录。RecoveryManager 使用 Arjuna Common Logging Framework (CLF) 提供的日志跟踪机制，它提供了一个隐藏了现有的 logging API 如 Jakarta "
+"log4j 或 JDK 1.4 logging API 之间的差异的高级别的接口。CLF 通过 Apache "
+"Commons Logging 框架间接处理日志，其配置假定存在于该框架内。"
#. Tag: para
#: Chapter.xml:58
@@ -333,7 +335,7 @@
"DEBUG, INFO, WARN, ERROR and FATAL. Defined Levels are ordered according to "
"their integer values as follows: DEBUG < INFO < WARN < ERROR < "
"FATAL."
-msgstr ""
+msgstr "用 CLF 应用程序来调用 logger 对象的日志调用。Logger 可以使用日志级别来决定具体的日志信息。每个日志信息都有一个相关的日志级别来表示重要和紧急程度。日志级别可以是 DEBUG、INFO、WARN、 ERROR 和 FATAL。按整形值的顺序排列为：DEBUG < INFO < WARN < ERROR < FATAL。"
#. Tag: para
#: Chapter.xml:61
@@ -343,7 +345,7 @@
"granularity an application may define. That is, when a log message is "
"provided to the logger with the DEBUG level, additional conditions can be "
"specified to determine if the log message is enabled or not."
-msgstr ""
+msgstr "CLF 提供按照定义的颗粒度过滤日志消息的扩展。这就是说，当 DEBUG 级别的日志消息被提供给 logger时，你可以指定其他的条件来决定是否启用这个日志消息。"
#. Tag: para
#: Chapter.xml:67
@@ -351,13 +353,13 @@
msgid ""
"These conditions are applied if and only the DEBUG level is enabled and the "
"log request performed by the application specifies debugging granularity."
-msgstr ""
+msgstr "只有启用了 DEBUG 级别且日志请求由应用程序专有的调试颗粒度执行时，才能应用这些条件。"
#. Tag: para
#: Chapter.xml:71
#, no-c-format
msgid "When enabled, Debugging is filtered conditionally on three variables:"
-msgstr ""
+msgstr "被启用后，日志消息根据 3 个变量进行有条件地过滤："
#. Tag: para
#: Chapter.xml:74
@@ -365,7 +367,7 @@
msgid ""
"Debugging level: this is where the log request with the DEBUG Level is "
"generated from, e.g., constructors or basic methods."
-msgstr ""
+msgstr "调试级别（Debugging level）：DEBUG 级别的日志请求产生的地方，如构造函数或基本方法。"
#. Tag: para
#: Chapter.xml:77
@@ -373,7 +375,7 @@
msgid ""
"Visibility level: the visibility of the constructor, method, etc. that "
"generates the debugging."
-msgstr ""
+msgstr "可见级别（Visibility level）：产生调试信息的构造函数、方法等的可见性。"
#. Tag: para
#: Chapter.xml:80
@@ -381,7 +383,7 @@
msgid ""
"Facility code: for instance the package or sub-module within which debugging "
"is generated, e.g., the object store."
-msgstr ""
+msgstr "Facility code：例如产生调试信息的包或子模块，如 ObjectStore。"
#. Tag: para
#: Chapter.xml:83
@@ -396,6 +398,8 @@
"enable debug messages. Finer debugging values used by the JBoss Transactions "
"are defined below:"
msgstr ""
+"根据这些变量，CLF 定义了 3 个接口。特定的产品可以按照需要实现自己的类。JBoss Transactions 使用 CLF 提供的缺省 Debugging level 和 Visibility level，但它定义自己的 Facility "
+"Code。JBoss Transactions 使用分配给 logger 对象的缺省的级别（DEBUG）。然而，它使用 finer debugging 特征来禁用或启用调试消息。JBoss Transactions 使用的 finer debugging 值有："
#. Tag: para
#: Chapter.xml:84
@@ -403,7 +407,7 @@
msgid ""
"Debugging level – JBoss Transactions uses the default values defined in the "
"class <classname>com.arjuna.common.util.logging.DebugLevel</classname>"
-msgstr ""
+msgstr "Debugging level – JBoss Transactions 使用 <classname>com.arjuna.common.util.logging.DebugLevel</classname> 类里定义的缺省值"
#. Tag: para
#: Chapter.xml:87
@@ -411,7 +415,7 @@
msgid ""
"NO_DEBUGGING: No diagnostics. A logger object assigned with this values "
"discard all debug requests"
-msgstr ""
+msgstr "NO_DEBUGGING: No diagnostics. 这个值分配的 Logger 对象丢弃所有的调试请求。"
#. Tag: para
#: Chapter.xml:90
@@ -420,7 +424,7 @@
"FULL_DEBUGGING: Full diagnostics. A Logger object assigned with this value "
"allows all debug requests if the facility code and the visibility level "
"match those allowed by the logger."
-msgstr ""
+msgstr "FULL_DEBUGGING: Full diagnostics. 如果 facility code 和 the visibility level 符合 logger 所允许的值，这个值分配的 Logger 对象允许所有的调试请求。"
#. Tag: para
#: Chapter.xml:93
@@ -438,55 +442,55 @@
#: Chapter.xml:99
#, no-c-format
msgid "DESTRUCTORS: Diagnostics from finalizers."
-msgstr ""
+msgstr "DESTRUCTORS: Diagnostics from finalizers."
#. Tag: para
#: Chapter.xml:102
#, no-c-format
msgid "CONSTRUCT_AND_DESTRUCT: Diagnostics from constructors and finalizers."
-msgstr ""
+msgstr "CONSTRUCT_AND_DESTRUCT: Diagnostics from constructors and finalizers."
#. Tag: para
#: Chapter.xml:105
#, no-c-format
msgid "FUNCTIONS: Diagnostics from functions."
-msgstr ""
+msgstr "FUNCTIONS: Diagnostics from functions."
#. Tag: para
#: Chapter.xml:108
#, no-c-format
msgid "OPERATORS: Diagnostics from operators, such as equals."
-msgstr ""
+msgstr "OPERATORS: Diagnostics from operators, such as equals."
#. Tag: para
#: Chapter.xml:111
#, no-c-format
msgid "FUNCS_AND_OPS: Diagnostics from functions and operations."
-msgstr ""
+msgstr "FUNCS_AND_OPS: Diagnostics from functions and operations."
#. Tag: para
#: Chapter.xml:114
#, no-c-format
msgid "ALL_NON_TRIVIAL: Diagnostics from all non-trivial operations."
-msgstr ""
+msgstr "ALL_NON_TRIVIAL: Diagnostics from all non-trivial operations."
#. Tag: para
#: Chapter.xml:117
#, no-c-format
msgid "TRIVIAL_FUNCS: Diagnostics from trivial functions."
-msgstr ""
+msgstr "TRIVIAL_FUNCS: Diagnostics from trivial functions."
#. Tag: para
#: Chapter.xml:120
#, no-c-format
msgid "TRIVIAL_OPERATORS: Diagnostics from trivial operations, and operators."
-msgstr ""
+msgstr "TRIVIAL_OPERATORS: Diagnostics from trivial operations, and operators."
#. Tag: para
#: Chapter.xml:123
#, no-c-format
msgid "ALL_TRIVIAL: Diagnostics from all trivial operations."
-msgstr ""
+msgstr "ALL_TRIVIAL: Diagnostics from all trivial operations."
#. Tag: para
#: Chapter.xml:126
@@ -494,43 +498,43 @@
msgid ""
"Visibility level – JBoss Transactions uses the default values defined in the "
"class <classname>com.arjuna.common.util.logging.VisibilityLevel</classname>"
-msgstr ""
+msgstr "Visibility level – JBoss Transactions 使用 <classname>com.arjuna.common.util.logging.VisibilityLevel</classname> 类里定义的缺省值"
#. Tag: para
#: Chapter.xml:129
#, no-c-format
msgid "VIS_NONE: No Diagnostic"
-msgstr ""
+msgstr "VIS_NONE: No Diagnostic"
#. Tag: para
#: Chapter.xml:132
#, no-c-format
msgid "VIS_PRIVATE : only from private methods."
-msgstr ""
+msgstr "VIS_PRIVATE : only from private methods."
#. Tag: para
#: Chapter.xml:135
#, no-c-format
msgid "VIS_PROTECTED only from protected methods."
-msgstr ""
+msgstr "VIS_PROTECTED only from protected methods."
#. Tag: para
#: Chapter.xml:138
#, no-c-format
msgid "VIS_PUBLIC only from public methods."
-msgstr ""
+msgstr "VIS_PUBLIC only from public methods."
#. Tag: para
#: Chapter.xml:141
#, no-c-format
msgid "VIS_PACKAGE only from package methods."
-msgstr ""
+msgstr "VIS_PACKAGE only from package methods."
#. Tag: para
#: Chapter.xml:144
#, no-c-format
msgid "VIS_ALL: Full Diagnostic"
-msgstr ""
+msgstr "VIS_ALL: Full Diagnostic"
#. Tag: para
#: Chapter.xml:147
@@ -538,49 +542,49 @@
msgid ""
"Facility Code – JBoss Transactions uses the following values defined in the "
"class <classname>com.arjuna.common.util.logging.VisibilityLevel</classname>"
-msgstr ""
+msgstr "Facility Code – JBoss Transactions 使用 <classname>com.arjuna.common.util.logging.VisibilityLevel</classname> 类定义的下列值"
#. Tag: para
#: Chapter.xml:150
#, no-c-format
msgid "FAC_ATOMIC_ACTION = 0x0000001 (atomic action core module)."
-msgstr ""
+msgstr "FAC_ATOMIC_ACTION = 0x0000001 (atomic action core module)."
#. Tag: para
#: Chapter.xml:153
#, no-c-format
msgid "FAC_BUFFER_MAN = 0x00000004 (state management (buffer) classes)."
-msgstr ""
+msgstr "FAC_BUFFER_MAN = 0x00000004 (state management (buffer) classes)."
#. Tag: para
#: Chapter.xml:156
#, no-c-format
msgid "FAC_ABSTRACT_REC = 0x00000008 (abstract records)."
-msgstr ""
+msgstr "FAC_ABSTRACT_REC = 0x00000008 (abstract records)."
#. Tag: para
#: Chapter.xml:159
#, no-c-format
msgid "FAC_OBJECT_STORE = 0x00000010 (object store implementations)."
-msgstr ""
+msgstr "FAC_OBJECT_STORE = 0x00000010 (object store implementations)."
#. Tag: para
#: Chapter.xml:162
#, no-c-format
msgid "FAC_STATE_MAN = 0x00000020 (state management and StateManager)."
-msgstr ""
+msgstr "FAC_STATE_MAN = 0x00000020 (state management and StateManager)."
#. Tag: para
#: Chapter.xml:165
#, no-c-format
msgid "FAC_SHMEM = 0x00000040 (shared memory implementation classes)."
-msgstr ""
+msgstr "FAC_SHMEM = 0x00000040 (shared memory implementation classes)."
#. Tag: para
#: Chapter.xml:168
#, no-c-format
msgid "FAC_GENERAL = 0x00000080 (general classes)."
-msgstr ""
+msgstr "FAC_GENERAL = 0x00000080 (general classes)."
#. Tag: para
#: Chapter.xml:171
@@ -589,25 +593,26 @@
"FAC_CRASH_RECOVERY = 0x00000800 (detailed trace of crash recovery module and "
"classes)."
msgstr ""
+"FAC_CRASH_RECOVERY = 0x00000800 (detailed trace of crash recovery module and "
+"classes)."
#. Tag: para
#: Chapter.xml:174
#, no-c-format
msgid "FAC_THREADING = 0x00002000 (threading classes)."
-msgstr ""
+msgstr "FAC_THREADING = 0x00002000 (threading classes)."
#. Tag: para
#: Chapter.xml:177
#, no-c-format
msgid "AC_JDBC = 0x00008000 (JDBC 1.0 and 2.0 support)."
-msgstr ""
+msgstr "AC_JDBC = 0x00008000 (JDBC 1.0 and 2.0 support)."
#. Tag: para
#: Chapter.xml:180
#, no-c-format
-msgid ""
-"FAC_RECOVERY_NORMAL = 0x00040000 (normal output for crash recovery manager)."
-msgstr ""
+msgid "FAC_RECOVERY_NORMAL = 0x00040000 (normal output for crash recovery manager)."
+msgstr "FAC_RECOVERY_NORMAL = 0x00040000 (normal output for crash recovery manager)."
#. Tag: para
#: Chapter.xml:183
@@ -616,7 +621,7 @@
"To ensure appropriate output, it is necessary to set some of the finer debug "
"properties explicitly in the <filename>CommonLogging.xml</filename> file, to "
"enable logging messages issued by the JBoss Transactions module."
-msgstr ""
+msgstr "为了保证合适的输出，我们有必要在 <filename>CommonLogging.xml</filename> 文件里对一些调试属性进行更详细的设置，启用 JBoss Transactions 模块登记的日志信息。"
#. Tag: para
#: Chapter.xml:184
@@ -629,6 +634,8 @@
"messages related to the Crash Recovery protocol and issued by the JBoss "
"Transactions module."
msgstr ""
+"描述启动和 RecoveryManager 的定期行为的消息使用 INFO 级别的输出。如果需要其他调试跟踪信息，你应该设置更详细的调试级别。例如，下面 CommonLogging.xml 里的配置，启用了和 Crash Recovery 协议相关以及 JBoss "
+"Transactions 产生的所有调试信息。"
#. Tag: programlisting
#: Chapter.xml:186
@@ -643,6 +650,14 @@
"<propertyname=\"com.arjuna.common.util.logging.VisibilityLevel\"\n"
" value=\"0xffffffff\"/>"
msgstr ""
+"<!-- Common logging related properties. -->\n"
+"<property\n"
+" name=\"com.arjuna.common.util.logging.DebugLevel\"\n"
+" value=\"0x00000000\"/>\n"
+"<propertyname=\"com.arjuna.common.util.logging.FacilityLevel\"\n"
+" value=\"0xffffffff\"/>\n"
+"<propertyname=\"com.arjuna.common.util.logging.VisibilityLevel\"\n"
+" value=\"0xffffffff\"/>"
#. Tag: para
#: Chapter.xml:189
@@ -650,7 +665,7 @@
msgid ""
"Two logger objects are provided, one manages I18N messages and a second does "
"not."
-msgstr ""
+msgstr "这里提供了两个 logger 对象，一个管理 I18N 消息而另外一个则处理其他消息。"
#. Tag: para
#: Chapter.xml:192
@@ -662,13 +677,13 @@
"disable INFO messages produced by the Recovery Manager, the logging level "
"could be set to the higher level: ERROR. Setting the level to ERROR means "
"that the RecoveryManager will only produce error, warning or fatal messages."
-msgstr ""
+msgstr "把常规恢复消息设置为 INFO 级别允许 RecoveryManager 产生适度的报告。如果没有发生任何事情，它仅仅报告模块的定期登录。要禁用 Recovery Manager 提供的 INFO 消息，调试级别可以设为更高的 ERROR 级别。这表示 RecoveryManager 将只产生错误、警告或致命错误信息。"
#. Tag: title
#: Chapter.xml:196
#, no-c-format
msgid "Periodic Recovery"
-msgstr ""
+msgstr "定期恢复"
#. Tag: para
#: Chapter.xml:197
@@ -683,6 +698,8 @@
"used are dynamically loaded, using properties found in the RecoveryManager "
"property file."
msgstr ""
+"RecoveryManager 扫描 ObjectStore 以及信息的其他位置，寻找需要恢复的事务和资源。这个扫描和恢复过程由恢复模块来执行（实现 com.arjuna.ats."
+"arjuna.recovery.RecoveryModule 接口的类的实例），每个都负责特定类别的事务和资源。恢复模块使用 RecoveryManager 属性文件里找到的属性动态地进行加载。"
#. Tag: para
#: Chapter.xml:198
@@ -701,6 +718,10 @@
"it is possible the original application process has crashed and the item is "
"a candidate for recovery."
msgstr ""
+"这个接口有两个方法：<literal>periodicWorkFirstPass</literal> 和 "
+"<literal>periodicWorkSecondPass</literal>。根据 <classname>com.arjuna.ats.arjuna.recovery.periodicRecoveryPeriod</"
+"classname> 属性定义的间隔，RecoveryManager 件将在每个属性上调用第一个 pass 方法，然后等待一段短暂的时间（由 <classname>com."
+"arjuna.ats.arjuna.recovery.recoveryBackoffPeriod</classname> 属性定义）。通常，在第一个 pass 方法里，模块通过扫描（例如 ObjectStore 的相关部分）来发现可疑的事务和资源（也就是提交过程进行一部分）。在第二个 pass 方法里，如果任何相同的事务或资源仍然可疑，那么原来的应用程序就有可能已经崩溃，这些事务和资源就需要进行恢复。"
#. Tag: para
#: Chapter.xml:199
@@ -718,6 +739,8 @@
"usually generating a warning. Recovery of such a transaction is the "
"RecoveryManager’s responsibility)."
msgstr ""
+"RecoveryManager 试图恢复仍然在原来进程里进行的事务有可能会破坏一致性。因此，恢复模块使用一个机制（在 <classname>com.arjuna.ats.arjuna.recovery.TransactionStatusManager</"
+"classname> 包里实现）来检查原来的进程是否仍然活动，且事务是否仍在进行。RecoveryManager 只在原始进程已经结束时才进行恢复，如果进程仍然活动，则在事务完成后进行。（如果服务器进程或主机崩溃了，但初始事务的基础仍然活动，事务也会完成并通常产生一个警告。RecoveryManager 也负责恢复这样的事务。）"
#. Tag: para
#: Chapter.xml:200
@@ -740,6 +763,8 @@
"thus require a “call to the original process to see if they are still in "
"progress"
msgstr ""
+"设置合适的时间间隔显然很重要。重复时间将是 <literal>periodicRecoveryPeriod</"
+"literal>、<literal>recoveryBackoffPeriod</literal> 和所有恢复模块扫描 ObjectStore 并试图恢复可疑事务所需时间的总和。恢复时间可能包括试图和已经崩溃或无法访问的进程或主机通信所需的连接超时时间（这是为什么在恢复系统里有机制避免试图恢复相同的事务）。总共的重复时间将影响在发生故障后资源保持无法访问状态的时间 － <literal>periodicRecoveryPeriod</literal> 应该相应地进行设置（缺省是 120 秒）。<literal>recoveryBackoffPeriod</literal> 可以相对较短（缺省是 10 秒） － 它的目的主要是减少事务作为恢复备选对象的次数（这需要访问原始进程，检查事务是否仍在进行）。"
#. Tag: para
#: Chapter.xml:203
@@ -748,7 +773,7 @@
"In previous versions of JBoss Transactions there was no contact mechanism, "
"and the backoff period had to be long enough to avoid catching transactions "
"in flight at all. From 3.0, there is no such risk."
-msgstr ""
+msgstr "JBoss Transactions 之前的版本里没有 contact 机制，你得把 backoff period 设置为足够久来避免缓存事务冲突。从 3.0 版本后，这不再是一个问题。"
#. Tag: para
#: Chapter.xml:206
@@ -767,6 +792,9 @@
"process might occur while a periodic recovery pass is in progress). The "
"default Recovery Extension settings are:"
msgstr ""
+"JBoss Transactions 提供了两个恢复模块（<classname>com.arjuna.ats."
+"arjuna.recovery.RecoveryModule</classname> 接口的实现），它们支持不同的事务恢复（包括 JDBC 恢复）。高级用户有可能创建自己的恢复模块并向 Recovery Manager 注册。恢复模块使用以“<classname>com.arjuna.ats.arjuna.recovery."
+"RecoveryExtension</classname>”开始的属性向 Recovery Manager 注册。它们将按照属性名称的顺序调用其定期恢复的 pass 方法（但请注意在定期恢复的 pass 方法运行时，可能会发生应用程序进程失效）。缺省的 Recovery Extension 设置是："
#. Tag: programlisting
#: Chapter.xml:208
@@ -778,12 +806,17 @@
"com.arjuna.ats.arjuna.recovery.recoveryExtension2 = \n"
" com.arjuna.ats.txoj.recovery.TORecoveryModule"
msgstr ""
+"com.arjuna.ats.arjuna.recovery.recoveryExtension1 = \n"
+" com.arjuna.ats.internal.ts.arjuna.recovery.AtomicActionRecoveryModule\n"
+"\n"
+"com.arjuna.ats.arjuna.recovery.recoveryExtension2 = \n"
+" com.arjuna.ats.txoj.recovery.TORecoveryModule"
#. Tag: title
#: Chapter.xml:211
#, no-c-format
msgid "Expired entry removal"
-msgstr ""
+msgstr "删除过期的条目"
#. Tag: para
#: Chapter.xml:212
@@ -806,12 +839,15 @@
"value is negative, the first scan is delayed until after the first interval "
"(using the absolute value)"
msgstr ""
+"恢复子系统的操作将导致 ObjectStore 创建的某些条目在常规情况下不会被删除。RecoveryManager 里有一个工具可以扫描和删除那些很旧的的条目。<classname>com.arjuna.ats.arjuna.recovery.ExpiryScanner</classname> 接口的实现执行这种扫描和删除。这个实现通过把类名作为以 <classname>com.arjuna."
+"ats.arjuna.recovery.expiryScanner</classname> 开始的属性的值来加载。RecoveryManager 按照属性 <classname>com."
+"arjuna.ats.arjuna.recovery.expiryScanInterval</classname> 指定的时间间隔调用每个加载的 Expiry Scanner 实现的 <command>scan()</command> 方法。这个值以小时为单位 － 缺省为 12。零值的 <classname>expiryScanInterval</classname> 将忽略任何过期扫描。如果这个值为正值，RecoveryManager 启动时将执行第一次扫描；如果为负值，第一次扫描将直到第一个间隔（使用绝对值）后才发生。"
#. Tag: para
#: Chapter.xml:213
#, no-c-format
msgid "The kinds of item that are scanned for expiry are:"
-msgstr ""
+msgstr "扫描过期的条目类型包括："
#. Tag: para
#: Chapter.xml:214
@@ -826,12 +862,14 @@
"– default is 12, zero means never expire). The expiry time should be greater "
"than the lifetime of any single JBoss Transactions-using process."
msgstr ""
+"TransactionStatusManager 条目：使用 JBoss Transactions 的每个应用程序进程创建的条目 － 它们包含允许 RecoveryManager 决定初始化事务的进程是否仍然活动、以及事务状态的信息。过期时间由属性 <classname>com.arjuna."
+"ats.arjuna.recovery.transactionStatusManagerExpiryTime</classname>（以小时为单位 － 缺省为 12，0 表示永不过期）设置。过期时间应该大于任何单个 JBoss Transactions-using 进程的生存时间。"
#. Tag: para
#: Chapter.xml:215
#, no-c-format
msgid "The Expiry Scanner properties for these are:"
-msgstr ""
+msgstr "Expiry Scanner 属性是："
#. Tag: programlisting
#: Chapter.xml:217
@@ -841,6 +879,9 @@
" com.arjuna.ats.internal.ts.arjuna.recovery."
"ExpiredTransactionStatusManagerScanner"
msgstr ""
+"com.arjuna.ats.arjuna.recovery.expiryScannerTransactionStatusManager =\n"
+" com.arjuna.ats.internal.ts.arjuna.recovery."
+"ExpiredTransactionStatusManagerScanner"
#. Tag: title
#: Chapter.xml:220
@@ -915,8 +956,7 @@
"normal execution of crash recovery. This is the result of multiple "
"concurrent attempts to perform recovery on the same transaction. It can be "
"safely ignored."
-msgstr ""
-"在失效切换的正常执行过程中，可能出现关于状态访问的 Object store 的警告。这是因为在相同的事务上执行多个并行的失效切换。它可以被忽略而无安全隐患。"
+msgstr "在失效切换的正常执行过程中，可能出现关于状态访问的 Object store 的警告。这是因为在相同的事务上执行多个并行的失效切换。它可以被忽略而无安全隐患。"
#. Tag: title
#: Chapter.xml:241
Modified: projects/docs/enterprise/4.3/Transactions/Administrators_Guide/zh-CN/Feedback.po
===================================================================
--- projects/docs/enterprise/4.3/Transactions/Administrators_Guide/zh-CN/Feedback.po 2008-06-24 04:07:59 UTC (rev 74950)
+++ projects/docs/enterprise/4.3/Transactions/Administrators_Guide/zh-CN/Feedback.po 2008-06-24 04:08:04 UTC (rev 74951)
@@ -8,7 +8,7 @@
"Project-Id-Version: Feedback\n"
"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
"POT-Creation-Date: 2008-06-05 22:49+0000\n"
-"PO-Revision-Date: 2008-06-16 10:45+1000\n"
+"PO-Revision-Date: 2008-06-24 11:47+1000\n"
"Last-Translator: Xi HUANG <xhuang at redhat.com>\n"
"Language-Team: <en at li.org>\n"
"MIME-Version: 1.0\n"
@@ -35,4 +35,9 @@
"be as specific as possible. If you have found an error, include the section "
"number and some of the surrounding text so we can find it easily."
msgstr ""
+"如果你在本指南里发现了印刷错误，或者你有改进该手册的建议，我们希望听到你的声音！请提交报告到 <ulink url=\"http://jira.jboss.com/jira/browse/JBPAPP\">JIRA</ulink> 并指明：产品：JBoss 企业级应用"
+"程序平台, 版本：<replaceable><version></replaceable>，组件：<emphasis>Doc</"
+"emphasis>。"
+"如果是改进本文档的建议，请尽量具体化；如果是其他错误，请指出章节号以及具体的内容"
+"，这样我们就可以尽快改正。"
Modified: projects/docs/enterprise/4.3/Transactions/Administrators_Guide/zh-CN/Revision_History.po
===================================================================
--- projects/docs/enterprise/4.3/Transactions/Administrators_Guide/zh-CN/Revision_History.po 2008-06-24 04:07:59 UTC (rev 74950)
+++ projects/docs/enterprise/4.3/Transactions/Administrators_Guide/zh-CN/Revision_History.po 2008-06-24 04:08:04 UTC (rev 74951)
@@ -1,20 +1,24 @@
+# translation of Revision_History.po to
# Language zh-CN translations for JBoss_Transactions_Administrators_Guide package.
+#
# Automatically generated, 2008.
-#
+# Xi HUANG <xhuang at redhat.com>, 2008.
msgid ""
msgstr ""
-"Project-Id-Version: JBoss_Transactions_Administrators_Guide 4.3\n"
+"Project-Id-Version: Revision_History\n"
"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
"POT-Creation-Date: 2008-06-05 22:49+0000\n"
-"PO-Revision-Date: 2008-06-05 22:49+0000\n"
-"Last-Translator: Automatically generated\n"
-"Language-Team: none\n"
+"PO-Revision-Date: 2008-06-24 11:43+1000\n"
+"Last-Translator: Xi HUANG <xhuang at redhat.com>\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: author
#: Revision_History.xml:9
#, no-c-format
msgid "<firstname></firstname> <surname></surname> <email></email>"
-msgstr ""
+msgstr "<firstname></firstname> <surname></surname> <email></email>"
+
More information about the jboss-cvs-commits
mailing list