[jboss-cvs] JBossAS SVN: r74901 - projects/docs/enterprise/4.3/Transactions/Administrators_Guide/zh-CN.
jboss-cvs-commits at lists.jboss.org
jboss-cvs-commits at lists.jboss.org
Mon Jun 23 09:03:00 EDT 2008
Author: xhuang at jboss.com
Date: 2008-06-23 09:03:00 -0400 (Mon, 23 Jun 2008)
New Revision: 74901
Modified:
projects/docs/enterprise/4.3/Transactions/Administrators_Guide/zh-CN/Chapter.po
Log:
update
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-23 12:36:26 UTC (rev 74900)
+++ projects/docs/enterprise/4.3/Transactions/Administrators_Guide/zh-CN/Chapter.po 2008-06-23 13:03:00 UTC (rev 74901)
@@ -8,7 +8,7 @@
"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-19 12:29+1000\n"
+"PO-Revision-Date: 2008-06-23 23:02+1000\n"
"Last-Translator: Xi HUANG <xhuang at redhat.com>\n"
"Language-Team: Chinese Simplified <kde-i18n-doc at lists.kde.org>\n"
"MIME-Version: 1.0\n"
@@ -85,23 +85,25 @@
"neither detect nor correct references to old object state by new operation "
"versions or vice versa."
msgstr ""
+"目前没有对类结构改变时对象或数据库重配置的版本控制的支持。这是我们还没解决的一个复杂的研究领域。目前，如果你修改了持久性对象的类的定义，你需要完全负责确保 "
+"Object Store 里的现存实例转换成新的结构。JBoss Transactions 既不能检测也不能改正通过新的操作版本对旧的对象状态的引用，反之亦然。"
#. Tag: para
#: Chapter.xml:19
#, no-c-format
msgid ""
"Object store management is critically important to the transaction service."
-msgstr ""
+msgstr "对于事务服务来说，Object store 的管理至关重要。"
#. Tag: title
#: Chapter.xml:24
#, no-c-format
msgid "ObjectStore management"
-msgstr ""
+msgstr "管理 ObjectStore "
#. Tag: para
#: Chapter.xml:25
-#, no-c-format
+#, fuzzy, no-c-format
msgid ""
"Within the transaction service installation, the object store is updated "
"regularly whenever transactions are created, or when Transactional Objects "
@@ -116,12 +118,15 @@
"is important that they realise this and do not simply delete the contents of "
"the object store assuming it is an exclusive resource."
msgstr ""
+"在事务访问安装里，只要有事务被创建或是用于 Java 的 Transactional Object 被使用，object store "
+"就会被更新。在无故障的环境里，唯一应该驻留在 object store 里的对象状态时那些代表用 Java API "
+"然而，如果发生了故障，事务日志可能保留在 object store 里，直到故障恢复机制已经恢复了它们所代表的事务。因此，"
#. Tag: title
#: Chapter.xml:28
#, no-c-format
msgid "JBoss Transactions runtime information"
-msgstr ""
+msgstr "JBoss Transactions 的运行信息"
#. Tag: para
#: Chapter.xml:29
@@ -132,6 +137,8 @@
"document representing the configuration information for that module. So, for "
"example:"
msgstr ""
+"组成 JBoss Transactions 的每个模块都拥有一个名为 info 的类。这些类都提供单一的 toString 方法来返回代表该模块的配置信息的 "
+"XML 文档。例如："
#. Tag: programlisting
#: Chapter.xml:31
@@ -152,12 +159,26 @@
" </configuration>\n"
"</module-info>"
msgstr ""
+"<module-info name=\"arjuna\">\n"
+" <source-identifier>unknown</source-identifier>\n"
+" <build-information>\n"
+" Arjuna Technologies [mlittle] (Windows 2000 5.0)\n"
+" </build-information>\n"
+" <version>unknown</version>\n"
+" <date>2002/06/15 04:06 PM</date>\n"
+" <notes></notes>\n"
+" <configuration>\n"
+" <properties-file dir=\"null\">arjuna.properties</"
+"properties-file>\n"
+" <object-store-root>null</object-store-root>\n"
+" </configuration>\n"
+"</module-info>"
#. Tag: title
#: Chapter.xml:34
#, no-c-format
msgid "Failure recovery administration"
-msgstr ""
+msgstr "失效切换管理"
#. Tag: para
#: Chapter.xml:35
@@ -175,12 +196,16 @@
"failure and is accessible afterward: this information is held in the "
"ActionStore, which is part of the ObjectStore."
msgstr ""
+"JBoss Transactions "
+"的失效切换子系统将确保在即使应用程序进程或主机崩溃或断开了网络连接的情况下，事务的结果都可以持续地应用到事务所影响的资源里。在主机（系统）崩溃或网络故障时，失效"
+"切换将直到系统或网络恢复时才进行，但原来的应用程序不需要重启 － 切换的责任委托给了 Recovery Manager "
+"进程（请参考下面内容）。失效切换要求和事务和资源相关的信息：这些信息保存在作为 ObjectStore 一部分的 ActionStore 里。"
#. Tag: para
#: Chapter.xml:38
#, no-c-format
msgid "If the ObjectStore is destroyed or modified, recovery may not be possible."
-msgstr ""
+msgstr "如果 ObjectStore 被销毁或修改，失效切换有可能无法进行。"
#. Tag: para
#: Chapter.xml:41
@@ -193,12 +218,15 @@
"resources, an attempt to activate the Transactional Object (as when trying "
"to get a lock) will fail."
msgstr ""
+"直到失效切换过程完成之前，故障发生时正进行的事务所影响的资源都可能无法访问。对于数据库资源而言，可能出现表或行被“in-doubt "
+"transactions”锁定。对于用于 Java 资源的 TransactionalObjects，试图激活 Transactional "
+"Object（尝试获取锁）将失败。"
#. Tag: title
#: Chapter.xml:43
#, no-c-format
msgid "The Recovery Manager"
-msgstr ""
+msgstr "Recovery Manager"
#. Tag: para
#: Chapter.xml:44
@@ -212,12 +240,16 @@
"RecoveryManager</classname>. To start the Recovery Manager issue the "
"following command:"
msgstr ""
+"JBoss Transactions 的失效切换（failure recovery）子系统要求为每个 ObjectStore（通常是网络上的每个运行 "
+"JBoss Transactions 应用程序的节点）运行独立的 Recovery Manager 进程。RecoveryManager 文件位于 <"
+"classname>com.arjuna.ats.arjuna.recovery.RecoveryManager</classname> 包里的 "
+"arjunacore jar 中。要启动 Recovery Manager，你可以使用下面的命令："
#. Tag: command
#: Chapter.xml:45
#, no-c-format
msgid "java com.arjuna.ats.arjuna.recovery.RecoveryManager"
-msgstr ""
+msgstr "java com.arjuna.ats.arjuna.recovery.RecoveryManager"
#. Tag: para
#: Chapter.xml:46
@@ -225,19 +257,19 @@
msgid ""
"If the <literal>-test</literal> flag is used with the Recovery Manager then "
"it will display a “Ready” message when initialised, i.e.,"
-msgstr ""
+msgstr "如果使用了 <literal>-test</literal> 标签，它将在初始化时显示“Ready”信息，也就是："
#. Tag: command
#: Chapter.xml:47
#, no-c-format
msgid "java com.arjuna.ats.arjuna.recovery.RecoveryManager -test"
-msgstr ""
+msgstr "java com.arjuna.ats.arjuna.recovery.RecoveryManager -test"
#. Tag: title
#: Chapter.xml:50
#, no-c-format
msgid "Configuring the Recovery Manager"
-msgstr ""
+msgstr "配置 Recovery Manager"
#. Tag: para
#: Chapter.xml:51
@@ -251,6 +283,10 @@
"in the main TransactionService properties file. Most of the entries are "
"specific to the Recovery Manager."
msgstr ""
+"RecoveryManager 读取 <filename>arjuna.properties</filename> "
+"文件里定义的属性，然后读取相同目录下的属性文件 <filename>RecoveryManager.properties</filename>"
+"。RecoveryManager 属性文件里的条目将覆盖 TransactionService 属性文件里相同的条目。大多数条目都是 Recovery "
+"Manager 所专有的。"
#. Tag: para
#: Chapter.xml:52
@@ -263,12 +299,14 @@
"other values (in the order of their appearance in the default version of the "
"file)"
msgstr ""
+"本发行版本提供一个缺省的 <filename>RecoveryManager.properties</filename> 版本 － "
+"它无需修改就可以使用，除了一些调试跟踪的字段（请参考下面的 Output）。本节剩下的内容将讨论将属性设置为其他值所相关的问题（按照在缺省版本里出现的顺序）。"
#. Tag: title
#: Chapter.xml:54
#, no-c-format
msgid "Output"
-msgstr ""
+msgstr "Output"
#. Tag: para
#: Chapter.xml:55
@@ -388,13 +426,13 @@
#: Chapter.xml:93
#, no-c-format
msgid "Additional Debugging Values are:"
-msgstr ""
+msgstr "其他的调试值有："
#. Tag: para
#: Chapter.xml:96
#, no-c-format
msgid "CONSTRUCTORS: Diagnostics from constructors."
-msgstr ""
+msgstr "CONSTRUCTORS: Diagnostics from constructors."
#. Tag: para
#: Chapter.xml:99
@@ -808,7 +846,7 @@
#: Chapter.xml:220
#, no-c-format
msgid "Errors and Exceptions"
-msgstr ""
+msgstr "错误和异常"
#. Tag: para
#: Chapter.xml:221
@@ -817,7 +855,7 @@
"In this section we shall cover the types of errors and exceptions which may "
"be thrown or reported during a transactional application and give probable "
"indications of their causes."
-msgstr ""
+msgstr "本节将涵盖在事务行应用程序运行时可能抛出或报告的错误和异常类型，并给出可能的原因。"
#. Tag: para
#: Chapter.xml:224
@@ -829,6 +867,8 @@
"throwing the exception. This is probably a transient problem and retrying "
"the invocation should succeed."
msgstr ""
+"NO_MEMORY：应用程序已耗尽内存（抛出 <classname>OutOfMemoryError</classname>）且 JBoss "
+"Transactions 在重新抛出这个异常时已经试图进行清理（通过运行 garbage collector）。这可能是一个暂时的问题，重试应该能够成功。"
#. Tag: para
#: Chapter.xml:227
@@ -840,6 +880,9 @@
"transactions have rolled back. If caught, the application should tidy up and "
"exit. If further work is attempted, application consistency may be violated."
msgstr ""
+"com.arjuna.ats.arjuna.exceptions."
+"FatalError：表示事务系统必须关闭的错误已经发生。在抛出这个错误之前，服务将确保所有的事务都进行了回滚。如果捕获了这个异常，应用程序应该清理并退出。如果"
+"进行进一步尝试，可能会破坏应用程序的一致性。"
#. Tag: para
#: Chapter.xml:230
@@ -850,6 +893,8 @@
"licence. The transaction service will not allow further forward progress for "
"existing or new transactions."
msgstr ""
+"com.arjuna.ats.arjuna.exceptions."
+"LicenceError：尝试以和当前许可证不一致的方式使用事务服务。事务服务将不会允许对现有的或新的事务进行进一步的行动。"
#. Tag: para
#: Chapter.xml:233
@@ -859,6 +904,8 @@
"the transaction service attempted to use the object store. Further forward "
"progress is not possible."
msgstr ""
+"com.arjuna.ats.arjuna.exceptions.ObjectStoreError：事务服务试图使用 object store "
+"时产生了错误。进一步的行动不被允许。"
#. Tag: para
#: Chapter.xml:236
@@ -869,12 +916,13 @@
"concurrent attempts to perform recovery on the same transaction. It can be "
"safely ignored."
msgstr ""
+"在失效切换的正常执行过程中，可能出现关于状态访问的 Object store 的警告。这是因为在相同的事务上执行多个并行的失效切换。它可以被忽略而无安全隐患。"
#. Tag: title
#: Chapter.xml:241
#, no-c-format
msgid "Selecting the JTA implementation"
-msgstr ""
+msgstr "选择 JTA 实现"
#. Tag: para
#: Chapter.xml:242
@@ -882,7 +930,7 @@
msgid ""
"Two variants of the JTA implementation are now provided and accessible "
"through the same interface. These are:"
-msgstr ""
+msgstr "目前可通过相同的接口访问两个 JTA 实现的变种。它们是："
#. Tag: para
#: Chapter.xml:245
@@ -891,7 +939,7 @@
"A purely local JTA, which only allows non-distributed JTA transactions to be "
"executed. This is the only version available with the JBoss Transactions "
"product."
-msgstr ""
+msgstr "纯本地的 JTA，它只允许执行非分布式的 JTA 事务。JBoss Transactions 产品里只有这个版本可用。"
#. Tag: para
#: Chapter.xml:248
@@ -900,7 +948,7 @@
"A remote, CORBA-based JTA, which allows distributed JTA transactions to be "
"executed. This version is only available with the ArjunaJTS product and "
"requires a supported CORBA ORB."
-msgstr ""
+msgstr "远程的，基于 CORBA 的 JTA，它允许执行分布式的 JTA 事务。它只在 ArjunaJTS 里可用且需要对 CORBA ORB 的支持。"
#. Tag: para
#: Chapter.xml:252
@@ -908,7 +956,7 @@
msgid ""
"both of these implementations are fully compatible with the transactional "
"JDBC driver provided with JBoss Transactions."
-msgstr ""
+msgstr "这两种实现都和 JBoss Transactions 提供的事务性的 JDBC 驱动完全兼容。"
#. Tag: para
#: Chapter.xml:255
@@ -916,7 +964,7 @@
msgid ""
"In order to select the local JTA implementation it is necessary to perform "
"the following steps:"
-msgstr ""
+msgstr "要选择本地的 JTA 实现，你必须执行下面的步骤："
#. Tag: para
#: Chapter.xml:258
@@ -926,6 +974,9 @@
"literal> is set to <literal>com.arjuna.ats.internal.jta.transaction."
"arjunacore.TransactionManagerImple</literal>."
msgstr ""
+"确保属性 <literal>com.arjuna.ats.jta.jtaTMImplementation</literal> 被设置为 <literal>"
+"com.arjuna.ats.internal.jta.transaction.arjunacore.TransactionManagerImple<"
+"/literal>。"
#. Tag: para
#: Chapter.xml:261
@@ -935,6 +986,9 @@
"literal> is set to <literal>com.arjuna.ats.internal.jta.transaction."
"arjunacore.UserTransactionImple</literal>."
msgstr ""
+"确保属性 <literal>com.arjuna.ats.jta.jtaUTImplementation</literal> 被设置为 <literal>"
+"com.arjuna.ats.internal.jta.transaction.arjunacore.UserTransactionImple<"
+"/literal>。"
#. Tag: para
#: Chapter.xml:265
@@ -942,5 +996,5 @@
msgid ""
"these settings are the default values for the properties and do not need to "
"be specified if the local implementation is required."
-msgstr ""
+msgstr "这些设置都是这些属性的缺省值，如果使用本地实现的话，你不需要进行指定。"
More information about the jboss-cvs-commits
mailing list