[jboss-svn-commits] JBL Code SVN: r23739 - labs/jbosstm/enterprise/tags/EAP_4_3_0/Transactions_JTA_Programmers_Guide/zh-CN.
jboss-svn-commits at lists.jboss.org
jboss-svn-commits at lists.jboss.org
Thu Nov 6 00:55:55 EST 2008
Author: xhuang at jboss.com
Date: 2008-11-06 00:55:55 -0500 (Thu, 06 Nov 2008)
New Revision: 23739
Modified:
labs/jbosstm/enterprise/tags/EAP_4_3_0/Transactions_JTA_Programmers_Guide/zh-CN/The_Resource_Manager.po
labs/jbosstm/enterprise/tags/EAP_4_3_0/Transactions_JTA_Programmers_Guide/zh-CN/Transaction_Recovery.po
Log:
update
Modified: labs/jbosstm/enterprise/tags/EAP_4_3_0/Transactions_JTA_Programmers_Guide/zh-CN/The_Resource_Manager.po
===================================================================
--- labs/jbosstm/enterprise/tags/EAP_4_3_0/Transactions_JTA_Programmers_Guide/zh-CN/The_Resource_Manager.po 2008-11-06 05:55:28 UTC (rev 23738)
+++ labs/jbosstm/enterprise/tags/EAP_4_3_0/Transactions_JTA_Programmers_Guide/zh-CN/The_Resource_Manager.po 2008-11-06 05:55:55 UTC (rev 23739)
@@ -1,14 +1,15 @@
# translation of The_Resource_Manager.po to
# Language zh-CN translations for package.
+#
# Automatically generated, 2008.
-#
+# Xi HUANG <xhuang at redhat.com>, 2008.
msgid ""
msgstr ""
"Project-Id-Version: The_Resource_Manager\n"
"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
"POT-Creation-Date: 2008-09-23 06:25+0000\n"
-"PO-Revision-Date: 2008-11-04 10:37+1000\n"
-"Last-Translator: \n"
+"PO-Revision-Date: 2008-11-06 15:55+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"
@@ -571,7 +572,7 @@
#: The_Resource_Manager.xml:203
#, no-c-format
msgid "Transaction timeouts"
-msgstr ""
+msgstr "事务超时"
#. Tag: para
#: The_Resource_Manager.xml:204
@@ -588,7 +589,7 @@
"exceed the default and in which case, if the timeout were not altered, the "
"resource manager would rollback before the transaction terminated and "
"subsequently cause the transaction to roll back as well."
-msgstr ""
+msgstr "事务可以和超时时间关联，这是为了控制生存时间。如果在超过超时时间后事务还未终止（提交或回滚），事务系统将自动将其回滚。<interfacename>XAResource</interfacename> 接口支持这样一个操作，它允许和当前事务关联的超时时间传递给资源管理者，并在被支持的情况下覆盖资源管理者关联的任何缺省超时时间。当长期运行的使用可能具有超过缺省值的生存时间时，这很有用，在这种情况下，如果没有修改超时时间，资源管理者将在事务终止前回滚并导致事务回滚。"
#. Tag: para
#: The_Resource_Manager.xml:207
@@ -598,7 +599,7 @@
"specified, then an implementation specific default value may be used. In the "
"case of JBossTS, how this default value is set depends upon which JTA "
"implementation you are using."
-msgstr ""
+msgstr "如果没有显性地为事务指定超时时间，或者是指定的值为 0，那么实现专有的缺省值将被使用。在 JBossTS 里，这个缺省值的设置取决于所使用的 JTA 实现。"
#. Tag: para
#: The_Resource_Manager.xml:212
@@ -608,6 +609,8 @@
"defaultTimeout</property> property value and give a timeout in seconds. The "
"default value is 60 seconds."
msgstr ""
+"本地 JTA：使用 <property>com.arjuna.ats.arjuna.coordinator."
+"defaultTimeout</property> 属性值并给出以秒为单位的超时时间。缺省值为 60 秒。"
#. Tag: para
#: The_Resource_Manager.xml:217
@@ -616,7 +619,7 @@
"JTS: use the <property>com.arjuna.ats.jts.defaultTimeout</property> property "
"value and give a timeout in seconds. The default value is 0, for instance, "
"transactions do not timeout."
-msgstr ""
+msgstr "JTS：使用 <property>com.arjuna.ats.jts.defaultTimeout</property> 属性值并给出以秒为单位的超时时间。缺省值为 0，也就是事务永不超时。"
#. Tag: para
#: The_Resource_Manager.xml:222
@@ -630,6 +633,9 @@
"nothing approach to whether or not <methodname>setTransactionTimeout</"
"methodname> is called on <interfacename>XAResource</interfacename> instances."
msgstr ""
+"可惜的是，有时候为资源管理者指定和事务相同的超时时间是不合适的。例如，如果系统管理员希望控制资源管理者的生存时间且并不希望（或不能）允许这个控制权转给外部的实体。目前，对于是否对 <interfacename>XAResource</interfacename> 实例调用 <methodname>setTransactionTimeout</"
+"methodname>，JBossTS 支持 all-or-"
+"nothing 方法。"
#. Tag: para
#: The_Resource_Manager.xml:225
@@ -641,12 +647,15 @@
"methodname> method of <classname>com.arjuna.ats.jta.common.Configuration</"
"classname> can be used."
msgstr ""
+"如果 <property>com.arjuna.ats.jta.xaTransactionTimeoutEnabled</property> 属性为 true（缺省值），那对于每个实例它都将被调用。或者可使用 <classname>com.arjuna.ats.jta.common.Configuration</"
+"classname> 的 <methodname>setXATransactionTimeoutEnabled</"
+"methodname> 方法。"
#. Tag: title
#: The_Resource_Manager.xml:231
#, no-c-format
msgid "Dynamic Registration"
-msgstr ""
+msgstr "动态注册"
#. Tag: para
#: The_Resource_Manager.xml:232
@@ -655,6 +664,8 @@
"Dynamic registration is not supported in <interfacename>XAResource</"
"interfacename> because of the following reasons:"
msgstr ""
+"<interfacename>XAResource</"
+"interfacename> 不支持动态注册，这是因为以下原因："
#. Tag: para
#: The_Resource_Manager.xml:237
@@ -664,7 +675,7 @@
"the resource manager are acquired dynamically when the application "
"explicitly requests a connection. These resources are enlisted with the "
"transaction manager on a needed basis."
-msgstr ""
+msgstr "在基于 Java 组件的应用服务器环境里，当应用程序显性地请求连接时将动态获取和资源管理者的连接。这些资源根据需要在事务管理者里进行登记。"
#. Tag: para
#: The_Resource_Manager.xml:242
@@ -674,5 +685,5 @@
"global transaction, the implementation can be done at the resource adapter "
"level via a private interface between the resource adapter and the "
"underlying resource manager."
-msgstr ""
+msgstr "如果资源管理者要求动态地注册到全局事务里，你可以在资源适配器级别通过资源适配器和底层资源管理者之间的私有接口实现。"
Modified: labs/jbosstm/enterprise/tags/EAP_4_3_0/Transactions_JTA_Programmers_Guide/zh-CN/Transaction_Recovery.po
===================================================================
--- labs/jbosstm/enterprise/tags/EAP_4_3_0/Transactions_JTA_Programmers_Guide/zh-CN/Transaction_Recovery.po 2008-11-06 05:55:28 UTC (rev 23738)
+++ labs/jbosstm/enterprise/tags/EAP_4_3_0/Transactions_JTA_Programmers_Guide/zh-CN/Transaction_Recovery.po 2008-11-06 05:55:55 UTC (rev 23739)
@@ -1,29 +1,32 @@
+# translation of Transaction_Recovery.po to
# Language zh-CN translations for package.
+#
# Automatically generated, 2008.
-#
+# Xi HUANG <xhuang at redhat.com>, 2008.
msgid ""
msgstr ""
-"Project-Id-Version: \n"
+"Project-Id-Version: Transaction_Recovery\n"
"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
"POT-Creation-Date: 2008-09-23 06:25+0000\n"
-"PO-Revision-Date: 2008-09-23 06:25+0000\n"
-"Last-Translator: Automatically generated\n"
-"Language-Team: none\n"
+"PO-Revision-Date: 2008-11-06 15:15+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: title
#: Transaction_Recovery.xml:6
#, no-c-format
msgid "Transaction Recovery"
-msgstr ""
+msgstr "事务恢复"
#. Tag: title
#: Transaction_Recovery.xml:8
#, no-c-format
msgid "Failure recovery"
-msgstr ""
+msgstr "失效切换"
#. Tag: para
#: Transaction_Recovery.xml:9
@@ -38,7 +41,7 @@
"resource factories that are used by the applications deployed on the system. "
"An example of such a resource factory is the JDBC <code>XADataSource</code> "
"object, which is a factory for the JDBC <code>XAConnection</code> objects."
-msgstr ""
+msgstr "在切换过程中，事务管理者需要和应用程序使用的所有资源管理者通信。对于每个资源管理者，事务管理者使用 <methodname>XAResource.recover</methodname> 方法来获取当前处于准备或即将完成状态的事务列表。通常，相同管理者配置素有的应用程序使用的事务性资源工厂。资源工厂的一个例子是 JDBC <code>XADataSource</code> 对象，它是用于 JDBC <code>XAConnection</code> 对象的工厂。"
#. Tag: para
#: Transaction_Recovery.xml:12
@@ -55,7 +58,7 @@
"<methodname>XAResource.recover</methodname> method to ask each resource "
"manager to return the transactions that are currently in a prepared or "
"heuristically completed state."
-msgstr ""
+msgstr "因为在系统失效时 <code>XAResource</code> 对象不是持久的，事务管理者需要获得代表资源管理者并在失效前已经参与事务的 <code>XAResource</code> 对象。例如，事务管理者可以通过使用 JNDI 查找机制来从每个事务资源工厂获取连接，然后再为每个连接获取相应的 <code>XAResource</code> 对象。事务管理者然后调用 <methodname>XAResource.recover</methodname> 方法来请求每个资源管理者目前处于准备或即将完成状态的事务。"
#. Tag: para
#: Transaction_Recovery.xml:16
@@ -71,6 +74,8 @@
"transactions irrespective of their node identifier and should be used with "
"caution."
msgstr ""
+"运行 XA 切换有必要告诉 JBossTS 它可以切换的 XID 的类型。JBossTS 创建的每个 XID 都有一个唯一的节点标识符，JBossTS 将只切换符合指定标识符的事务和状态。节点标识符应该通过名称以 <property>com."
+"arjuna.ats.jta.xaRecoveryNode</property> 开始的属性提供给 JBossTS，这也可以是多个值。\"*\" 将使 JBossTS 恢复（或者回滚）所有的事务而管其节点标识符，这要谨慎使用。"
#. Tag: para
#: Transaction_Recovery.xml:20
@@ -79,7 +84,7 @@
"If using the JBossJTA JDBC 2.0 driver, then JBossJTA will take care of all "
"<interfacename>XAResource</interfacename> crash recovery automatically. "
"Otherwise one of the following recovery mechanisms will be used:"
-msgstr ""
+msgstr "如果使用 JBossJTA JDBC 2.0 驱动，JBossJTA 将自动处理所有 <interfacename>XAResource</interfacename> 崩溃切换。否则将使用下列的切换机制中的一个："
#. Tag: para
#: Transaction_Recovery.xml:25
@@ -89,7 +94,7 @@
"will be saved during transaction commitment, and used during recovery. It is "
"assumed that the recreated <code>XAResource</code> is valid and can be used "
"to drive recovery on the associated database."
-msgstr ""
+msgstr "如果 <code>XAResource</code> 是可序列化的，在事务提交时序列化格式将被保存并在切换时使用。我们假设重新创建的 <code>XAResource</code> 是有效的且可用来驱动相关联的数据库的切换。"
#. Tag: para
#: Transaction_Recovery.xml:30
@@ -101,6 +106,10 @@
"jta.recovery.XARecoveryResource</interfacename> interfaces are used. These "
"are documented in the JDBC chapters on failure recovery."
msgstr ""
+"<interfacename>com.arjuna.ats.jta.recovery.XAResourceRecovery</"
+"interfacename>、<interfacename>com.arjuna.ats.jta.recovery."
+"XARecoveryResourceManager</interfacename> 和 <interfacename>com.arjuna.ats."
+"jta.recovery.XARecoveryResource</interfacename> 接口被使用。这些在失效切换的 JDBC 章节里提交。"
#. Tag: para
#: Transaction_Recovery.xml:36
@@ -110,12 +119,15 @@
"interfacename> was deprecated in favor of <interfacename>XAResourceRecovery</"
"interfacename>. Users are encouraged to move to his new interface."
msgstr ""
+"在 JBossTS 3.3，<interfacename>XAConnectionRecovery</"
+"interfacename> 接口被替代为 <interfacename>XAResourceRecovery</"
+"interfacename>。我们鼓励用户使用新的接口。"
#. Tag: title
#: Transaction_Recovery.xml:43
#, no-c-format
msgid "Recovering XAConnections"
-msgstr ""
+msgstr "切换 XA 连接"
#. Tag: para
#: Transaction_Recovery.xml:44
@@ -133,6 +145,8 @@
"<interfacename>com.arjuna.ats.jta.recovery.XAResourceRecovery</"
"interfacename>, one for each database that may be used by an application."
msgstr ""
+"当进行失效切换时，JBossJTA 要求有在失效前重新连接数据库的能力，这样才能解决未决的事务。大多数连接信息在正常执行过程中将由事务服务保存，并在重新创建连接时使用。然而，不是所有这样的信息都会在失效前被保存（例如，失效可能发生在保存之前而在数据库连接使用之后）。为了重新创建这些连接，为应用程序使用的每个数据库提供 JBossJTA 接口 <interfacename>com.arjuna.ats.jta.recovery.XAResourceRecovery</"
+"interfacename> 的实现是必需的。"
#. Tag: para
#: Transaction_Recovery.xml:48
@@ -140,7 +154,7 @@
msgid ""
"If using the transactional JDBC 2.0 driver provided with JBossJTA, then no "
"additional work is necessary in order to ensure that recovery occurs."
-msgstr ""
+msgstr "如果使用 JBossJTA 提供的事务性的 JDBC 2.0 驱动，确保切换发生则不需要任何其他设置。"
#. Tag: para
#: Transaction_Recovery.xml:52
@@ -153,13 +167,15 @@
"jta.recovery.XAResourceRecovery</property> will be assumed to represent one "
"of these instances, and its value should be the class name. For example:"
msgstr ""
+"为了将每个 <code>XAResourceRecovery</"
+"code> 实例通知切换系统，你需要通过属性变量指定其类名。我们假设属性文件里找到的或者在运行时注册的、名称以 <property>com.arjuna.ats."
+"jta.recovery.XAResourceRecovery</property> 开始的任何变量将代表这些实例，其值应该为类名。例如："
#. Tag: screen
#: Transaction_Recovery.xml:55
#, no-c-format
-msgid ""
-"com.arjuna.ats.jta.recovery.XAResourceRecoveryOracle=com.foo.barRecovery"
-msgstr ""
+msgid "com.arjuna.ats.jta.recovery.XAResourceRecoveryOracle=com.foo.barRecovery"
+msgstr "com.arjuna.ats.jta.recovery.XAResourceRecoveryOracle=com.foo.barRecovery"
#. Tag: para
#: Transaction_Recovery.xml:56
@@ -167,7 +183,7 @@
msgid ""
"Additional information that will be passed to the instance when it is "
"created may be specified after a semicolon:"
-msgstr ""
+msgstr "在实例创建时将被传递给实例的其他信息也可在分号后指定："
#. Tag: screen
#: Transaction_Recovery.xml:59
@@ -176,18 +192,20 @@
"com.arjuna.ats.jta.recovery.XAResourceRecoveryOracle=com.foo.barRecovery;"
"myData=hello"
msgstr ""
+"com.arjuna.ats.jta.recovery.XAResourceRecoveryOracle=com.foo.barRecovery;"
+"myData=hello"
#. Tag: para
#: Transaction_Recovery.xml:61
#, no-c-format
msgid "These properties need to go into the JTA section of the property file."
-msgstr ""
+msgstr "这些属性需要在属性文件的 JTA 部分设置。"
#. Tag: para
#: Transaction_Recovery.xml:65
#, no-c-format
msgid "Any errors will be reported during recovery."
-msgstr ""
+msgstr "切换过程任何错误将被报告。"
#. Tag: screen
#: Transaction_Recovery.xml:68
@@ -202,12 +220,20 @@
" public boolean hasMoreResources ();\n"
"};"
msgstr ""
+"public interface XAResourceRecovery\n"
+"{\n"
+" public XAResource getXAResource () throws SQLException;\n"
+" \n"
+" public boolean initialise (String p);\n"
+" \n"
+" public boolean hasMoreResources ();\n"
+"};"
#. Tag: para
#: Transaction_Recovery.xml:69
#, no-c-format
msgid "Each method should return the following information:"
-msgstr ""
+msgstr "每个方法应该返回下列的信息："
#. Tag: para
#: Transaction_Recovery.xml:74
@@ -218,7 +244,7 @@
"after the first semi-colon) will be passed to the object. The object can "
"then use this information in an implementation specific manner to initialise "
"itself, for example."
-msgstr ""
+msgstr "<methodname>initialise</methodname>：一旦实例被创建，关于属性值的任何其他信息（在第一个分号之后的任何设置）将被传递给这个对象。然后它可以以实现专有的形式使用这些信息来初始化自己，例如："
#. Tag: para
#: Transaction_Recovery.xml:79
@@ -233,6 +259,8 @@
"recovery sweep and the instance will not be used further until the next "
"recovery scan."
msgstr ""
+"<methodname>hasMoreResources</methodname>：每个 <code>XAResourceRecovery</"
+"code> 实现可以提供多个 <code>XAResource</code> 实例。在对 <methodname>getXAResource</methodname> 进行任何调用之前，<methodname>hasMoreResources</methodname> 被调用来决定是否需要获取更多的连接。如果返回 false，在这个切换过程中 <methodname>getXAResource</methodname> 将不会再被调用，在下一次切换扫描之前这个实例也不会被使用。"
#. Tag: para
#: Transaction_Recovery.xml:84
@@ -246,6 +274,9 @@
"source, and should obviously be sufficient to create new <code>XAResources</"
"code> that can be used to drive recovery."
msgstr ""
+"<methodname>getXAResource</methodname>：返回 <code>XAResource</code> 对象的一个实例。它怎样被创建的（构造函数的参数是如何获得的）取决于 <code>XAResourceRecovery</"
+"code> 实现。这个类的构造函数的参数应该和在创建初始驱动或数据源时使用的那些类的参数类似，且足够来创建用于驱动切换的新的 <code>XAResources</"
+"code>。"
#. Tag: para
#: Transaction_Recovery.xml:90
@@ -255,13 +286,13 @@
"during each sweep of the recovery manager then you should ensure that once "
"<methodname>hasMoreResources</methodname> returns false to indicate the end "
"of work for the current scan it then returns true for the next recovery scan."
-msgstr ""
+msgstr "如果你希望在切换管理者扫描过程中调用 <code>XAResourceRecovery</code> 实例，你应该确保一旦 <methodname>hasMoreResources</methodname> 返回 false 来指明当前扫描的结束，它应该返回 true 来进行下一次切换扫描。"
#. Tag: title
#: Transaction_Recovery.xml:97
#, no-c-format
msgid "Shipped XAResourceRecovery implementations"
-msgstr ""
+msgstr "附带的 XAResourceRecovery 实现"
#. Tag: para
#: Transaction_Recovery.xml:98
@@ -271,7 +302,7 @@
"implementation dependant, requiring developers to provide their own "
"<interfacename>XAResourceRecovery</interfacename> instances. However, "
"JBossTS ships with several out-of-the-box implementations that may be useful."
-msgstr ""
+msgstr "<interfacename>XA</interfacename> 数据源的切换有时候可能依赖于相关的实现，要求开发者提供自己的<interfacename>XAResourceRecovery</interfacename> 实例。然而，JBossTS 带有几个可能有用的实现。"
#. Tag: para
#: Transaction_Recovery.xml:103
@@ -282,6 +313,8 @@
"creation and from which it will read the database URL, username and "
"password. For example:"
msgstr ""
+"<interfacename>com.arjuna.ats.internal.jdbc.recovery.OracleXARecovery</"
+"interfacename>：它期望在创建时指定 XML 属性文件，从中它可以读取数据库 URL、用户名和密码。例如："
#. Tag: screen
#: Transaction_Recovery.xml:106
@@ -298,6 +331,16 @@
" </properties>\n"
"</transaction-service>"
msgstr ""
+"<?xml version=\"1.0\" encoding=\"UTF-8\"?>\n"
+" \n"
+"<transaction-service>\n"
+" <properties name=\"jdbc\" type=\"system\">\n"
+" <property name=\"DatabaseURL\" value=\"jdbc:oracle:thin:"
+"@hostname:1521:sid\"/>\n"
+" <property name=\"UserName\" value=\"username\"/>\n"
+" <property name=\"Password\" value=\"password\"/>\n"
+" </properties>\n"
+"</transaction-service>"
#. Tag: para
#: Transaction_Recovery.xml:109
@@ -309,6 +352,8 @@
"upon creation and from which it will read the database JNDI name, username "
"and password. For example:"
msgstr ""
+"<interfacename>com.arjuna.ats.internal.jdbc.recovery.JDBCXARecovery</"
+"interfacename>：这个切换实现应该可用于任何通过 JNDI 开放的数据源。它期望在创建时指定 XML 属性文件，从中它可以读取数据库 URL、用户名和密码。例如："
#. Tag: screen
#: Transaction_Recovery.xml:112
@@ -327,3 +372,16 @@
" </properties>\n"
"</transaction-service>"
msgstr ""
+"<?xml version=\"1.0\" encoding=\"UTF-8\"?>\n"
+" \n"
+"<transaction-service>\n"
+" <properties name=\"jdbc\" type=\"system\">\n"
+" <property name=\"DatabaseJNDIName\" value=\"java:ExampleDS"
+"\"/>\n"
+" <property name=\"UserName\" value=\"username\"/"
+">\n"
+" <property name=\"Password\" value=\"password\"/"
+">\n"
+" </properties>\n"
+"</transaction-service>"
+
More information about the jboss-svn-commits
mailing list