[jboss-cvs] JBossAS SVN: r89000 - 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
Mon May 18 04:25:51 EDT 2009
Author: xhuang at jboss.com
Date: 2009-05-18 04:25:51 -0400 (Mon, 18 May 2009)
New Revision: 89000
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-18 08:14:28 UTC (rev 88999)
+++ projects/docs/enterprise/4.3.3/Server_Configuration_Guide/zh-CN/Transactions.po 2009-05-18 08:25:51 UTC (rev 89000)
@@ -1,30 +1,32 @@
+# translation of Transactions.po to
# Language /tmp/mike/JBEAP420/JBAS translations for JBEAP package.
-# Copyright (C) 2007 Free Software Foundation, Inc.
+# Copyright (C) 2007, 2009 Free Software Foundation, Inc.
# Automatically generated, 2007.
#
msgid ""
msgstr ""
-"Project-Id-Version: JBEAP 420\n"
+"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: 2001-02-09 01:25+0100\n"
-"Last-Translator: Automatically generated\n"
-"Language-Team: none\n"
+"PO-Revision-Date: 2009-05-18 18:21+1000\n"
+"Last-Translator: Xi HUANG\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
#: Transactions.xml:6
-#, fuzzy, no-c-format
+#, no-c-format
msgid "Transactions on JBoss"
-msgstr "Naming on JBoss"
+msgstr "JBoss 的事务处理"
#. Tag: subtitle
#: Transactions.xml:7
-#, fuzzy, no-c-format
+#, no-c-format
msgid "The JTA Transaction Service"
-msgstr "JNDI 命名服务"
+msgstr "JTA 事务服务"
#. Tag: para
#: Transactions.xml:8
@@ -41,12 +43,14 @@
"discussion of the MBeans available for integration of alternate transaction "
"managers."
msgstr ""
+"本章讨论 JBoss 的事务管理以及 JBossTX 架构。JBossTX 架构允许使用任何的 Java Transaction API "
+"(JTA) 事务管理者实现。JBossTX 包括一个快速的 VM 内部的兼容 JTA 事务管理者的实现，它被用作缺省的事务管理者。我们将介绍关于 JTA 里事务的关键性概念和主张，为后来的 JBossTX 架构讨论提供足够的背景知识。然后我们将讨论组成 JBossTX 架构的接口以及集成其他事务管理者的 MBean。"
#. Tag: title
#: Transactions.xml:12
#, no-c-format
msgid "Transaction/JTA Overview"
-msgstr ""
+msgstr "事务/JTA 概述"
#. Tag: para
#: Transactions.xml:13
@@ -57,7 +61,7 @@
"resources having ACID properties. ACID is an acronym for atomicity, "
"consistency, isolation and durability, the four important properties of "
"transactions. The meanings of these terms is:"
-msgstr ""
+msgstr "在本次讨论里，我们把事务定义成包含涉及一个或多个具有 ACID 属性的共享资源的一个或多个操作的工作单元。ACID 是原子性（atomicity）、一致性（consistency）、独立性（isolation）和持久性（durability）四个重要属性的缩写。这些术语的意思是："
#. Tag: para
#: Transactions.xml:18
@@ -67,17 +71,15 @@
"This means that either all the work done in the transaction must be "
"performed, or none of it must be performed. Doing part of a transaction is "
"not allowed."
-msgstr ""
+msgstr "<emphasis role=\"bold\">原子性</emphasis>：事务必须是原子的。这意味着要么所有的工作都在事务里完成，要么所有工作都不执行。不允许执行事务的一部分。"
#. Tag: para
#: Transactions.xml:23
-#, fuzzy, no-c-format
+#, no-c-format
msgid ""
"<emphasis role=\"bold\">Consistency</emphasis>: When a transaction is "
"completed, the system must be in a stable and consistent condition."
-msgstr ""
-"<emphasis role=\"bold\">INFO</emphasis>：操作不应该修改MBean组件的状态(读操"
-"作)。"
+msgstr "<emphasis role=\"bold\">一致性</emphasis>：当事务完成时，系统必须处于稳定和一致的状态。"
#. Tag: para
#: Transactions.xml:28
@@ -88,7 +90,7 @@
"transaction is not visible to other transactions until the transaction is "
"committed, and that each process in a multi-user system can be programmed as "
"if it was the only process accessing the system."
-msgstr ""
+msgstr "<emphasis role=\"bold\">独立性</emphasis>：不同的事务必须彼此独立。这意味着某个事务里已完成的部分工作只有在该事务提交后才能对其他事务可见，多用户系统里的每个进程都必须进行单独编程，就好像只有一个进程访问系统一样。"
#. Tag: para
#: Transactions.xml:33
@@ -98,7 +100,7 @@
"transaction are made persistent when it is committed. When a transaction is "
"committed, its changes will not be lost, even if the server crashes "
"afterwards."
-msgstr ""
+msgstr "<emphasis role=\"bold\">持久性</emphasis>：事务期间的修改在事务提交后将是持久的。当事务被提交后，即使之后服务器崩溃，它的修改不会丢失。"
#. Tag: para
#: Transactions.xml:38
@@ -110,7 +112,7 @@
"from account A to account B by subtracting M from account A and adding M to "
"account B. This operation must be done in a transaction, and all four ACID "
"properties are important."
-msgstr ""
+msgstr "为了解释这些概念，让我们来看看一个简单的关于银行帐号的应用程序。这个程序有一个含有多个帐号的数据库。所有帐号的总额必须总是为 0。从帐号 A 移走金额 M 到帐号 B 需要把 M 从帐号 A 扣除并把 M 添加到帐号 B 里。这些操作必须在一个事务里完成，所有的四个 ACID 属性都很重要。"
#. Tag: para
#: Transactions.xml:41
@@ -119,7 +121,7 @@
"The atomicity property means that both the withdrawal and deposit is "
"performed as an indivisible unit. If, for some reason, both cannot be done "
"nothing will be done."
-msgstr ""
+msgstr "原子性属性表示取款和存款都以不可分割的单元执行。如果出于某种原因，两者不能都完成，那么就都不完成。"
#. Tag: para
#: Transactions.xml:44
@@ -127,7 +129,7 @@
msgid ""
"The consistency property means that after the transaction, the sum of the "
"amounts of all accounts must still be 0."
-msgstr ""
+msgstr "一致性属性表示在事务完成后，所有帐号的金额之和必须仍然为 0。"
#. Tag: para
#: Transactions.xml:47
@@ -142,7 +144,7 @@
"processes read the amount of account A at the same time, and each "
"independently added or subtracted something before writing the new amount to "
"the database, the first change would be incorrectly overwritten by the last."
-msgstr ""
+msgstr "当有多个银行职员同时使用系统时，独立性属性就很重要了。取款或存款可以三个步骤实现：首先，从数据库里读取帐号；然后根据读取的金额加上或减去某个金额；最后把新的金额写入数据库。如果没有独立性就会出现一些问题。例如，如果两个进程同时读取帐号 A 的金额，然后在写回数据库之前各自添加或减少某个金额，那么第一次的修改会被第二次不正确地覆盖掉。"
#. Tag: para
#: Transactions.xml:50
@@ -151,13 +153,13 @@
"The durability property is also important. If a money transfer transaction "
"is committed, the bank must trust that some subsequent failure cannot undo "
"the money transfer."
-msgstr ""
+msgstr "持久性属性也很重要。如果提交了一个转帐交易，银行必须确保随后发生的故障不会影响已完成的转帐。"
#. Tag: title
#: Transactions.xml:54
#, no-c-format
msgid "Pessimistic and optimistic locking"
-msgstr ""
+msgstr "悲观和乐观锁"
#. Tag: para
#: Transactions.xml:55
@@ -166,7 +168,7 @@
"Transactional isolation is usually implemented by locking whatever is "
"accessed in a transaction. There are two different approaches to "
"transactional locking: Pessimistic locking and optimistic locking."
-msgstr ""
+msgstr "事务的独立性通常通过访问事务的锁来实现。事务性锁有两种不同的方式：悲观锁和乐观锁。"
#. Tag: para
#: Transactions.xml:58
@@ -184,7 +186,7 @@
"in the other process being delayed until the account lock is released, or "
"that the process transaction will be rolled back. The lock exists until the "
"transaction has either been committed or rolled back."
-msgstr ""
+msgstr "悲观锁的劣势是资源将在第一次被访问时被锁住一直到事务完成，在这个期间其他事务不能访问这个资源。如果大多数事务都简单地锁住资源且不进行修改，排他锁可能滥用因为它会导致锁争用，此时乐观锁可能就是更好的办法了。使用悲观锁，锁以 fail-safe 的方式来应用。在银行程序的例子里，只要在事务里访问了帐号，它就会被锁住。试图在其他事务里使用它会导致其他进程阻塞至这个锁被释放，或者其他进程所在的事务被回滚。这个锁一直会存在，直到事务被提交或回滚。"
#. Tag: para
#: Transactions.xml:61
@@ -200,7 +202,7 @@
"when the resource was first accessed in the transaction. If the two states "
"differ, a conflicting update was made, and the transaction will be rolled "
"back."
-msgstr ""
+msgstr "使用乐观锁，资源在第一次被事务访问时并不会实际上被锁住。相反，此时资源的状态将被保留。其他事务可以并发访问资源，这也存在修改冲突的可能性。在提交的时候，当资源将被更新到持久性存储里时，资源的状态将被再次读取并和第一次被访问时的状态进行比较。如果两个状态不同，那更新就会冲突，从而事务会被回滚。"
#. Tag: para
#: Transactions.xml:64
@@ -212,13 +214,13 @@
"amount is about to be updated. If the amount has changed since the "
"transaction began, the transaction will fail itself, otherwise the new "
"amount is written to persistent storage."
-msgstr ""
+msgstr "在银行程序的例子里，帐号的金额在它第一次被访问时被存储。如果事务修改了这个金额，在进行更新前会再次读取金额。如果在事务开始后金额已经发生了变动，那么这个事务将无法完成，否则新的金额将被写入到持久性存储里。"
#. Tag: title
#: Transactions.xml:70
#, no-c-format
msgid "The components of a distributed transaction"
-msgstr ""
+msgstr "分布式事务的组件"
#. Tag: para
#: Transactions.xml:71
@@ -226,7 +228,7 @@
msgid ""
"There are a number of participants in a distributed transaction. These "
"include:"
-msgstr ""
+msgstr "分布式事务有许多参与者，其中包括："
#. Tag: para
#: Transactions.xml:76
@@ -236,7 +238,7 @@
"distributed across the transactional system. It manages and coordinates the "
"work involved in the transaction. The transaction manager is exposed by the "
"<literal>javax.transaction.TransactionManager</literal> interface in JTA."
-msgstr ""
+msgstr "<emphasis role=\"bold\">事务管理者（Transaction Manager）</emphasis>：这个组件分布于整个事务系统里。它管理和协调涉及事务的工作。事务管理者通过 JTA 里的 <literal>javax.transaction.TransactionManager</literal> 接口进行开放。"
#. Tag: para
#: Transactions.xml:81
@@ -245,7 +247,7 @@
"<emphasis role=\"bold\">Transaction Context</emphasis>: A transaction "
"context identifies a particular transaction. In JTA the corresponding "
"interface is <literal>javax.transaction.Transaction</literal>."
-msgstr ""
+msgstr "<emphasis role=\"bold\">事务上下文（Transaction Context）</emphasis>：事务上下文表示特定的事务。在 JTA 里对应的接口是 <literal>javax.transaction.Transaction</literal>。"
#. Tag: para
#: Transactions.xml:86
@@ -257,7 +259,7 @@
"called the transaction originator. A transaction client is either an "
"explicit or implicit user of JTA interfaces and has no interface "
"representation in the JTA."
-msgstr ""
+msgstr "<emphasis role=\"bold\">事务性客户（Transactional Client）</emphasis>：事务性客户可以在单个事务内调用一个或多个事务性对象上的操作。启动事务的事务性客户被成为事务发起人（Originator）。事务性客户可以是 JTA 接口的显性或隐形用户且不对应 JTA 里的任何接口。"
#. Tag: para
#: Transactions.xml:91
@@ -267,7 +269,7 @@
"object is an object whose behavior is affected by operations performed on it "
"within a transactional context. A transactional object can also be a "
"transactional client. Most Enterprise Java Beans are transactional objects."
-msgstr ""
+msgstr "<emphasis role=\"bold\">事务性对象（Transactional Object）</emphasis>：事务性对象的行为被事务性上下文里执行的操作所影响。事务性对象也可以是一个事务性客户。大多数 EJB 都是事务性对象。"
#. Tag: para
#: Transactions.xml:96
@@ -290,7 +292,7 @@
#: Transactions.xml:104
#, no-c-format
msgid "The two-phase XA protocol"
-msgstr ""
+msgstr "两阶段的 XA 协议"
#. Tag: para
#: Transactions.xml:105
@@ -301,7 +303,7 @@
"all of is rolled back. If only a single recoverable resource is involved in "
"the transaction, the task of the transaction manager is simple: It just has "
"to tell the resource to commit the changes to stable storage."
-msgstr ""
+msgstr "当事务准备提交时，事务管理者将负责确保所有内容都提交，或者都进行回滚。如果只涉及单个的可恢复资源，事务管理者的任务就很简单：它只是告诉资源把修改的内容提交到持久性存储里。"
#. Tag: para
#: Transactions.xml:108
@@ -436,8 +438,7 @@
#. Tag: para
#: Transactions.xml:152
#, no-c-format
-msgid ""
-"The branch qualifier denotes a particular branch of the global transaction."
+msgid "The branch qualifier denotes a particular branch of the global transaction."
msgstr ""
#. Tag: para
@@ -497,22 +498,19 @@
#. Tag: para
#: Transactions.xml:183
#, no-c-format
-msgid ""
-"Participants may not allow their resources to be locked for long durations."
+msgid "Participants may not allow their resources to be locked for long durations."
msgstr ""
#. Tag: para
#: Transactions.xml:188
#, no-c-format
-msgid ""
-"The communication infrastructure between participants may not be reliable."
+msgid "The communication infrastructure between participants may not be reliable."
msgstr ""
#. Tag: para
#: Transactions.xml:193
#, no-c-format
-msgid ""
-"Some of the ACID properties of traditional transactions are not mandatory."
+msgid "Some of the ACID properties of traditional transactions are not mandatory."
msgstr ""
#. Tag: para
@@ -540,8 +538,7 @@
#. Tag: para
#: Transactions.xml:213
#, no-c-format
-msgid ""
-"Transactions that have to be rolled back have the concept of compensation."
+msgid "Transactions that have to be rolled back have the concept of compensation."
msgstr ""
#. Tag: para
@@ -633,3 +630,4 @@
"JTS and XTS components are not supported for JBoss Enterprise Application "
"Platform 4.x"
msgstr ""
+
More information about the jboss-cvs-commits
mailing list