[jboss-cvs] JBossAS SVN: r89031 - projects/docs/enterprise/4.3.3/Server_Configuration_Guide/zh-CN.
jboss-cvs-commits at lists.jboss.org
jboss-cvs-commits at lists.jboss.org
Tue May 19 01:43:14 EDT 2009
Author: xhuang at jboss.com
Date: 2009-05-19 01:43:14 -0400 (Tue, 19 May 2009)
New Revision: 89031
Modified:
projects/docs/enterprise/4.3.3/Server_Configuration_Guide/zh-CN/Transactions.po
Log:
update
Modified: projects/docs/enterprise/4.3.3/Server_Configuration_Guide/zh-CN/Transactions.po
===================================================================
--- projects/docs/enterprise/4.3.3/Server_Configuration_Guide/zh-CN/Transactions.po 2009-05-19 05:33:54 UTC (rev 89030)
+++ projects/docs/enterprise/4.3.3/Server_Configuration_Guide/zh-CN/Transactions.po 2009-05-19 05:43:14 UTC (rev 89031)
@@ -1,15 +1,16 @@
# translation of Transactions.po to
# Language /tmp/mike/JBEAP420/JBAS translations for JBEAP package.
# Copyright (C) 2007, 2009 Free Software Foundation, Inc.
+#
# Automatically generated, 2007.
-#
+# Xi HUANG <xhuang at redhat.com>, 2009.
msgid ""
msgstr ""
"Project-Id-Version: Transactions\n"
"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
"POT-Creation-Date: 2009-01-20 02:37+0000\n"
-"PO-Revision-Date: 2009-05-18 18:21+1000\n"
-"Last-Translator: Xi HUANG\n"
+"PO-Revision-Date: 2009-05-19 15:42+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"
@@ -286,7 +287,7 @@
"like JBossMQ are examples of recoverable resources. A recoverable resource "
"is represented using the <literal>javax.transaction.xa.XAResource</literal> "
"interface in JTA."
-msgstr ""
+msgstr "<emphasis role=\"bold\">可恢复资源（Recoverable Resource）</emphasis>：可恢复资源是一个事务性对象，如果事务提交，它的状态保存在持久性存储里，如果事务回滚，它的状态可恢复到事务起始时的状态。在提交时，如果涉及多个可恢复资源，事务管理者使用两阶段的 XA 协议来和可恢复资源进行通信以确保事务的完整性。事务性数据库和消息中介如 JBossMQ 都是可恢复资源的例子。可恢复资源用 JTA 里的 <literal>javax.transaction.xa.XAResource</literal> 接口来代表。"
#. Tag: title
#: Transactions.xml:104
@@ -315,7 +316,7 @@
"maintain the atomic property of the transaction. The reason for this is that "
"if one recoverable resource has committed and another fails to commit, part "
"of the transaction would be committed and the other part rolled back."
-msgstr ""
+msgstr "当事务涉及多个可恢复资源时，提交的管理就更复杂了。简单地要求每个可恢复资源把修改提交到持久性存储来维护事务的原子属性是不够的。其原因是如果一个可恢复资源已经提交而另外一个失败了，部分事务将被提交而其他部分将回滚。"
#. Tag: para
#: Transactions.xml:111
@@ -328,7 +329,7 @@
"When a recoverable resource indicates it is prepared to commit the "
"transaction, it has ensured that it can commit the transaction. The resource "
"is still able to rollback the transaction if necessary as well."
-msgstr ""
+msgstr "文了绕开这个问题，我们采用了两阶段 XA 协议。在实际的提交阶段前，XA 协议涉及一个额外的准备（prepare）阶段。在请求任何可恢复资源提交前，事务管理者请求所有可恢复资源准备提交。当可恢复资源指示它准备好提交时，就表示它可以提交事务了。如果有必要，此时资源仍可以回滚。"
#. Tag: para
#: Transactions.xml:114
@@ -342,13 +343,13 @@
"manager asking all the recoverable resources to commit the transaction. "
"Because all the recoverable resources have indicated they are prepared, this "
"step cannot fail."
-msgstr ""
+msgstr "所以，第一个阶段是事务管理者请求所有的可恢复资源准备提交。如果任何可恢复资源没有准备成功，事务将被回滚。但是，如果所有的可恢复资源都指示它们准备好了，XA 协议的第二阶段就开始了。事务管理者将请求所有的可恢复资源提交事务。因为所有的可恢复资源都已经表示准备好了，所以这个步骤不可能失败。"
#. Tag: title
#: Transactions.xml:120
#, no-c-format
msgid "Heuristic exceptions"
-msgstr ""
+msgstr "试探性异常（Heuristic exception）"
#. Tag: para
#: Transactions.xml:121
@@ -363,7 +364,7 @@
"parts of the transaction being committed while other parts are rolled back, "
"thus violating the atomicity property of transaction and possibly leading to "
"data integrity corruption."
-msgstr ""
+msgstr "在分布式环境里，通信失败时常发生。如果事务管理者和可恢复资源间的通信在一段时间后还没有响应，可恢复资源可以决定单方面地提交或回滚。这样的决定被称为试探性决定（heuristic decision）。这是事务系统里最坏的情况之一，因为这会导致事务的一部分被提交而另外一部分被回滚，从而违背了事务的原子性属性并可能导致数据完整性错误。"
#. Tag: para
#: Transactions.xml:124
@@ -376,7 +377,7 @@
"that is saved in stable storage depends on the type of recoverable resource "
"and is not standardized. The idea is that a system manager can look at the "
"data, and possibly edit the resource to correct any data integrity problems."
-msgstr ""
+msgstr "因为试探性异常的危险性，作出试探性决定的可恢复资源被要求在持久性存储里维护所有的信息，一直到事务管理者通知可忽略这些信息为止。保存在持久性存储里的关于试探性决定的实际数据取决于可恢复资源的类型，它不是标准化的。系统管理者可以查看这些数据，并可以编辑资源来纠正任何数据完整性问题。"
#. Tag: para
#: Transactions.xml:127
@@ -391,6 +392,8 @@
"resource when it is asked to commit to indicate that a heuristic decision "
"was made and that all relevant updates have been rolled back."
msgstr ""
+"下面是 JTA 定义的几种不同的试探性异常。当可恢复资源被要求回滚并报告已作出试探性决定且已提交所有相关的更新时抛出 <literal>javax.transaction.HeuristicCommitException</literal>。相方的情况是 <literal>javax.transaction."
+"HeuristicRollbackException</literal>，它在可恢复资源被要求提交并指明已作出试探性决定且已回滚所有相关的更新时抛出。"
#. Tag: para
#: Transactions.xml:130
@@ -402,13 +405,13 @@
"transaction manager throws this exception when some recoverable resources "
"did a heuristic commit, while other recoverable resources did a heuristic "
"rollback."
-msgstr ""
+msgstr "<literal>javax.transaction.HeuristicMixedException</literal> 是最糟糕的试探性异常。它在事务的一部分被提交而其他部分被回滚时抛出。当某些可恢复资源进行试探性提交而其他可恢复资源进行试探性回滚时，事务管理者抛出这个异常。"
#. Tag: title
#: Transactions.xml:136
#, no-c-format
msgid "Transaction IDs and branches"
-msgstr ""
+msgstr "事务 ID 和分支"
#. Tag: para
#: Transactions.xml:137
@@ -417,7 +420,7 @@
"In JTA, the identity of transactions is encapsulated in objects implementing "
"the <literal>javax.transaction.xa.Xid</literal> interface. The transaction "
"ID is an aggregate of three parts:"
-msgstr ""
+msgstr "在 JTA 里，事务的标识以实现 <literal>javax.transaction.xa.Xid</literal> 接口的对象进行封装。事务的 ID 由三个部分组成："
#. Tag: para
#: Transactions.xml:142
@@ -425,7 +428,7 @@
msgid ""
"The format identifier indicates the transaction family and tells how the "
"other two parts should be interpreted."
-msgstr ""
+msgstr "format 标识符表示事务族以及如何翻译其他两部分。"
#. Tag: para
#: Transactions.xml:147
@@ -433,13 +436,13 @@
msgid ""
"The global transaction id identified the global transaction within the "
"transaction family."
-msgstr ""
+msgstr "global 事务 ID 标识事务族里的全局事务。"
#. Tag: para
#: Transactions.xml:152
#, no-c-format
msgid "The branch qualifier denotes a particular branch of the global transaction."
-msgstr ""
+msgstr "branch 限定符指定全局事务里的一个特定分支。"
#. Tag: para
#: Transactions.xml:157
@@ -448,13 +451,13 @@
"Transaction branches are used to identify different parts of the same global "
"transaction. Whenever the transaction manager involves a new recoverable "
"resource in a transaction it creates a new transaction branch."
-msgstr ""
+msgstr "事务分支（Branch）用于表示相同全局事务的不同部分。每当事务管理者使用事务里新的可恢复资源时，它就会创建一个新的事务分支。"
#. Tag: title
#: Transactions.xml:165
#, no-c-format
msgid "JTS support"
-msgstr ""
+msgstr "JTS 支持"
#. Tag: para
#: Transactions.xml:166
@@ -468,12 +471,14 @@
"standards and leads the market in providing many advanced features such as "
"fully distributed transactions and ORB portability with POA support."
msgstr ""
+"JBoss Transactions 是一个 100% Java 的分布式事务管理系统的实现，它基于 Sun Microsystems 的 J2EE Java "
+"Transaction Service (JTS) 标准。我们对 JTS 的实现利用了 J2EE 和 EJB 标准推荐的用于事务互用性的 Object Management Group's (OMG) Object Transaction Service (OTS) 模型，它通过提供许多高级功能而领先于市场其他产品，如完全分布式的事务和支持 POA 的 ORB 可移植性。"
#. Tag: title
#: Transactions.xml:172
#, no-c-format
msgid "Web Services Transactions"
-msgstr ""
+msgstr "Web Services 的事务"
#. Tag: para
#: Transactions.xml:173
@@ -485,7 +490,7 @@
"advent of the Internet and Web services, the scenario that is now emerging "
"requires involvement of participants unknown to each other in distributed "
"transactions. These transactions have the following characteristics:"
-msgstr ""
+msgstr "在传统的 ACID 事务系统里，事务是短期的，资源（如数据库）在事务期间被锁住，且参与者高度信任对方。而互联网和 Web Service 里的分布式事务则涉及互不相识的参与者。这些事务具有下列的特征："
#. Tag: para
#: Transactions.xml:178
@@ -493,25 +498,25 @@
msgid ""
"Transactions may be of a long duration, sometimes lasting hours, days, or "
"more."
-msgstr ""
+msgstr "事务可能具有持续较长时间，有时候是数小时、天甚至更长。"
#. Tag: para
#: Transactions.xml:183
#, no-c-format
msgid "Participants may not allow their resources to be locked for long durations."
-msgstr ""
+msgstr "参与者可能允许不会允许其资源被长时间地锁住。"
#. Tag: para
#: Transactions.xml:188
#, no-c-format
msgid "The communication infrastructure between participants may not be reliable."
-msgstr ""
+msgstr "参与者间的通信架构可能不可靠。"
#. Tag: para
#: Transactions.xml:193
#, no-c-format
msgid "Some of the ACID properties of traditional transactions are not mandatory."
-msgstr ""
+msgstr "传统事务的某些 ACID 事务不是强制性的。"
#. Tag: para
#: Transactions.xml:198
@@ -519,7 +524,7 @@
msgid ""
"A transaction may succeed even if only some of the participants choose to "
"confirm and others cancel."
-msgstr ""
+msgstr "即使某些参与者选择继续而其他一些参与者选择取消，事务也可能成功完成。"
#. Tag: para
#: Transactions.xml:203
@@ -527,19 +532,19 @@
msgid ""
"All participants may choose to have their own coordinator (Transaction "
"Manager), because of lack of trust."
-msgstr ""
+msgstr "由于缺乏信任，所有的参与者可能选择拥有自己的协调者（事务管理者）。"
#. Tag: para
#: Transactions.xml:208
#, no-c-format
msgid "All activities are logged."
-msgstr ""
+msgstr "所有的活动都会记录日志。"
#. Tag: para
#: Transactions.xml:213
#, no-c-format
msgid "Transactions that have to be rolled back have the concept of compensation."
-msgstr ""
+msgstr "必须回滚的事务具有补偿的概念。"
#. Tag: para
#: Transactions.xml:218
@@ -554,12 +559,15 @@
"designed to support multiple coordination protocols and therefore helps to "
"future-proof transactional applications."
msgstr ""
+"JBoss Transactions 提供构建可互用的、可靠的、多方的基于 Web Service 的应用程序所需的所有组件，从而为 Web services 的事务提供了缺省的支持。它的编程接口基于 XML Transactioning "
+"(JAXTX) 的 Java API 并支持 WS-"
+"AtomicTransaction 和 WS-BusinessActivity 规格。JBossTS 4.2 的目的是支持多重协调协议从而构建不会过时的事务性应用程序。"
#. Tag: title
#: Transactions.xml:224
-#, fuzzy, no-c-format
+#, no-c-format
msgid "Configuring JBoss Transactions"
-msgstr "配置 JBoss"
+msgstr "配置 JBoss 事务"
#. Tag: para
#: Transactions.xml:225
@@ -568,19 +576,19 @@
"JBossTS is configured through the jbossjts-properties.xml property file. You "
"should consult the JBossTS documentation for all of the configurable options "
"it supports."
-msgstr ""
+msgstr "JBossTS 通过 jbossjts-properties.xml 属性文件进行配置。关于它所支持的所有可配置选项，你应该参考 JBossTS 文档。"
#. Tag: title
#: Transactions.xml:231
#, no-c-format
msgid "Local versus distributed transactions"
-msgstr ""
+msgstr "本地和分布式事务的对比"
#. Tag: title
#: Transactions.xml:233
#, no-c-format
msgid "Local Transactions"
-msgstr ""
+msgstr "本地事务"
#. Tag: para
#: Transactions.xml:234
@@ -592,13 +600,13 @@
"for the JTA. Databases and message queues running as separate processes may "
"still be enlisted as XAResources provided they have drivers that support "
"this."
-msgstr ""
+msgstr "本地事务只允许在一个 JVM 里征用资源，它不会跨越多个进程实例（也就是 VM）。然而，独立的客户端 JVM 仍可以管理 JTA 的事务边界（begin/commit/rollback）。如果有合适的驱动支持，作为独立进程运行的数据库和消息队列仍然可以作为 XAResource 资源征用。"
#. Tag: title
#: Transactions.xml:237
-#, fuzzy, no-c-format
+#, no-c-format
msgid "Distributed Transactions"
-msgstr "分布式垃圾收集（Distributed Garbage Collection）"
+msgstr "分布式事务"
#. Tag: para
#: Transactions.xml:238
@@ -609,7 +617,7 @@
"participants (e.g., XAResources) that are located within multiple VMs but "
"the transaction is coordinated in a separate VM (or co-located with one of "
"the participants)."
-msgstr ""
+msgstr "如果事务跨越多个进程实例（也就是 VM），它则被视为分布式的事务。分布式事务通常将包含位于多个 VM 内的参与者（如 XAResource），但事务会在单独的 VM（或与某个参与者并存）里进行协调。"
#. Tag: para
#: Transactions.xml:240
@@ -621,7 +629,7 @@
"communication, or the Web Services transactions component, which uses SOAP/"
"HTTP. Although the JTS/XTS component can be used with JBoss Enterprise "
"Application Platform, it is not a supported part of the platform."
-msgstr ""
+msgstr "JBossTS 提供本地和分布式事务。如果你的架构要求分布式事务，则你应该考虑使用使用 CORBA 通信的 JBossTS 的 JTS 实现，或者是使用 SOAP/HTTP 的 Web Services 事务组件。虽然 JTS/XTS 组件可以和 JBoss 企业级应用程序平台一起使用，但它并不属于支持服务的范畴。"
#. Tag: para
#: Transactions.xml:243
@@ -629,5 +637,5 @@
msgid ""
"JTS and XTS components are not supported for JBoss Enterprise Application "
"Platform 4.x"
-msgstr ""
+msgstr "JBoss EAP 4.X 不支持 JTS 和 XTS 组件。"
More information about the jboss-cvs-commits
mailing list