[jboss-svn-commits] JBL Code SVN: r23625 - 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
Wed Oct 29 21:40:25 EDT 2008
Author: xhuang at jboss.com
Date: 2008-10-29 21:40:25 -0400 (Wed, 29 Oct 2008)
New Revision: 23625
Modified:
labs/jbosstm/enterprise/tags/EAP_4_3_0/Transactions_JTA_Programmers_Guide/zh-CN/An_Introduction_to_the_JTA.po
labs/jbosstm/enterprise/tags/EAP_4_3_0/Transactions_JTA_Programmers_Guide/zh-CN/JDBC_and_Transactions.po
labs/jbosstm/enterprise/tags/EAP_4_3_0/Transactions_JTA_Programmers_Guide/zh-CN/Transactions.po
labs/jbosstm/enterprise/tags/EAP_4_3_0/Transactions_JTA_Programmers_Guide/zh-CN/Using_JBossJTA_in_Application_Servers.po
Log:
update
Modified: labs/jbosstm/enterprise/tags/EAP_4_3_0/Transactions_JTA_Programmers_Guide/zh-CN/An_Introduction_to_the_JTA.po
===================================================================
--- labs/jbosstm/enterprise/tags/EAP_4_3_0/Transactions_JTA_Programmers_Guide/zh-CN/An_Introduction_to_the_JTA.po 2008-10-29 19:56:54 UTC (rev 23624)
+++ labs/jbosstm/enterprise/tags/EAP_4_3_0/Transactions_JTA_Programmers_Guide/zh-CN/An_Introduction_to_the_JTA.po 2008-10-30 01:40:25 UTC (rev 23625)
@@ -8,7 +8,7 @@
"Project-Id-Version: An_Introduction_to_the_JTA\n"
"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
"POT-Creation-Date: 2008-09-23 06:25+0000\n"
-"PO-Revision-Date: 2008-10-28 11:44+1000\n"
+"PO-Revision-Date: 2008-10-30 10:35+1000\n"
"Last-Translator: Xi HUANG <xhuang at redhat.com>\n"
"Language-Team: <en at li.org>\n"
"MIME-Version: 1.0\n"
@@ -19,15 +19,14 @@
#. Tag: title
#: An_Introduction_to_the_JTA.xml:6
#, no-c-format
-#, fuzzy
msgid "An Introduction to the JTA"
-msgstr "简介"
+msgstr "JTA 简介"
#. Tag: title
#: An_Introduction_to_the_JTA.xml:8
#, no-c-format
msgid "The Java Transaction API"
-msgstr ""
+msgstr "Java Transaction API"
#. Tag: para
#: An_Introduction_to_the_JTA.xml:9
@@ -42,7 +41,7 @@
"are geared more for applications which require XA resource integration "
"capabilities, rather than the more general resources which the other APIs "
"allow."
-msgstr ""
+msgstr "对于程序员来说，许多事务标准指定的接口通常都过于涉及底层细节。因此，Sun Microsystems 已经设计了更高级别的接口来开发分布式事务性应用程序。请注意，这些接口仍然面向较低级别，要求程序员处理状态管理和并发性。此外，它们更适合需要 XA 资源集成能力而不是其他 API 允许的普通资源的应用程序。"
#. Tag: para
#: An_Introduction_to_the_JTA.xml:12
@@ -50,7 +49,7 @@
msgid ""
"With reference to [JTA99], distributed transaction services typically "
"involve a number of participants:"
-msgstr ""
+msgstr "根据 [JTA99] 协议，分布式事务服务通常涉及许多参与者："
#. Tag: para
#: An_Introduction_to_the_JTA.xml:17
@@ -59,7 +58,7 @@
"Application server: which provides the infrastructure required to support "
"the application run-time environment which includes transaction state "
"management, for example, an EJB server."
-msgstr ""
+msgstr "应用服务器：它提供支持运行环境（包括事务状态管理）所需的基础结构，如 EJB 服务器。"
#. Tag: para
#: An_Introduction_to_the_JTA.xml:22
@@ -68,7 +67,7 @@
"Transaction manager: provides the services and management functions required "
"to support transaction demarcation, transactional resource management, "
"synchronisation and transaction context propagation."
-msgstr ""
+msgstr "事务管理者：提供支持事务限界、事务性资源管理、同步和事务上下文传递所需的服务和管理功能。"
#. Tag: para
#: An_Introduction_to_the_JTA.xml:27
@@ -83,6 +82,8 @@
"transaction manager to communicate transaction association, transaction "
"completion and recovery."
msgstr ""
+"资源管理者：（通过资源适配器<footnote> <para> 应用服务器或客户端使用资源适配器（Resource "
+"Adapter）来连接资源管理者。其中一个例子是用于连接关系型数据库的 JDBC 驱动。</para> </footnote>）为应用程序提供对资源的访问。资源管理者通过实现事务资源接口来管理事务关联、完成和切换。"
#. Tag: para
#: An_Introduction_to_the_JTA.xml:36
@@ -91,7 +92,7 @@
"A communication resource manager (CRM): supports transaction context "
"propagation and access to the transaction service for incoming and outgoing "
"requests."
-msgstr ""
+msgstr "通信资源管理者（CRM）：支持转入和转出请求的事务上下文传递以及对事务服务的访问。"
#. Tag: para
#: An_Introduction_to_the_JTA.xml:41
@@ -104,7 +105,7 @@
"transaction services. The JTA is a high-level application interface that "
"allows a transactional application to demarcate transaction boundaries, and "
"contains also contains a mapping of the X/Open XA protocol."
-msgstr ""
+msgstr "从事务管理者的角度来看，并不需要开放实际的事务服务实现；只需要定义高级别的接口来允许用户驱动事务限界、资源征用、同步和切换。JTA 是一个高级别的应用程序接口，它允许事务性应用程序限定事务边界并包含 X/Open XA 协议的映射。"
#. Tag: para
#: An_Introduction_to_the_JTA.xml:45
@@ -112,5 +113,5 @@
msgid ""
"The JTA support provided by JBossJTA is compliant with the 1.0.1 "
"specification."
-msgstr ""
+msgstr "JBossJTA 提供的 JTA 支持兼容 1.0.1 规格。"
Modified: labs/jbosstm/enterprise/tags/EAP_4_3_0/Transactions_JTA_Programmers_Guide/zh-CN/JDBC_and_Transactions.po
===================================================================
--- labs/jbosstm/enterprise/tags/EAP_4_3_0/Transactions_JTA_Programmers_Guide/zh-CN/JDBC_and_Transactions.po 2008-10-29 19:56:54 UTC (rev 23624)
+++ labs/jbosstm/enterprise/tags/EAP_4_3_0/Transactions_JTA_Programmers_Guide/zh-CN/JDBC_and_Transactions.po 2008-10-30 01:40:25 UTC (rev 23625)
@@ -8,8 +8,8 @@
"Project-Id-Version: JDBC_and_Transactions\n"
"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
"POT-Creation-Date: 2008-09-23 06:25+0000\n"
-"PO-Revision-Date: 2008-10-29 11:50+1000\n"
-"Last-Translator: \n"
+"PO-Revision-Date: 2008-10-30 11:25+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"
@@ -140,7 +140,6 @@
#. Tag: para
#: JDBC_and_Transactions.xml:64
#, no-c-format
-#, fuzzy
msgid ""
"The JBossJTA approach to incorporating JDBC connections within transactions "
"is to provide transactional JDBC drivers through which all interactions "
@@ -152,8 +151,7 @@
"code>, which implements the <interfacename>java.sql.Driver</interfacename> "
"interface."
msgstr ""
-""
-"这些驱动拦截所有的调用，确保它们向合适的事务注册并由之驱动。明显地，如果数据库不是事务性的，那么 ACID 属性也不能被保证。这个驱动是 <code>com.arjuna.ats.jdbc.TransactionalDriver</"
+"JBossJTA 把 JDBC 连接合并在事务里来提供所有交互都涉及的事务性 JDBC 驱动。这些驱动拦截所有的调用，确保它们向合适的事务注册并由之驱动。明显地，如果数据库不是事务性的，那么 ACID 属性也不能被保证。这个驱动是 <code>com.arjuna.ats.jdbc.TransactionalDriver</"
"code>，它实现了 <interfacename>java.sql.Driver</interfacename> 接口。"
#. Tag: title
@@ -408,6 +406,8 @@
"myXADataSource</property>), the application is not tied at build time to "
"only use a specific (XA)DataSource implementation."
msgstr ""
+"为了允许 JDBC 驱动使用任意的数据源而不需知道相关实现的细节，数据源通常通过 JNDI 获取。专有的 (XA)DataSource 可以用合适的 JNDI 实现创建和注册，之后应用程序（或 JDBC 驱动）可以绑定并使用它。既然 JNDI 只允许应用程序把 (XA)DataSource 作为接口实例（如 <property>javax.sql.XADataSource</property>）而不是实现类的实例（ <property>com.mydb."
+"myXADataSource</property>）对待，应用程序就不会在构建时只使用专门的 (XA)DataSource 实现。"
#. Tag: para
#: JDBC_and_Transactions.xml:145
@@ -418,7 +418,7 @@
"<code>XADataSource</code> instance and store it in an appropriate JNDI "
"implementation. Details of how to do this can be found in the JDBC 2.0 "
"tutorial available at JavaSoft. An example is show below:"
-msgstr ""
+msgstr "为了获取 <classname>TransactionalDriver</classname> 类来使用已注册 JNDI 的 <code>XADataSource</code>，你首先得创建一个 <code>XADataSource</code> 并将其存储在合适的 JNDI 实现里。相关细节可以在 JavaSoft 的 JDBC 2.0 教程里找到。下面是一个例子："
#. Tag: screen
#: JDBC_and_Transactions.xml:148
@@ -435,6 +435,16 @@
" \n"
"ctx.bind(\"jdbc/foo\", ds);"
msgstr ""
+"XADataSource ds = MyXADataSource();\n"
+"Hashtable env = new Hashtable();\n"
+"String initialCtx = PropertyManager.getProperty(\"Context."
+"INITIAL_CONTEXT_FACTORY\");\n"
+" \n"
+"env.put(Context.INITIAL_CONTEXT_FACTORY, initialCtx);\n"
+" \n"
+"initialContext ctx = new InitialContext(env);\n"
+" \n"
+"ctx.bind(\"jdbc/foo\", ds);"
#. Tag: para
#: JDBC_and_Transactions.xml:149
@@ -506,7 +516,7 @@
"several classes which are for specific JDBC 2.0 implementations, and these "
"can be selected at runtime by the application setting the "
"<property>dynamicClass</property> property appropriately:"
-msgstr ""
+msgstr "许多 JDBC 2.0 实现都提供 <interfacename>XADataSources</interfacename> 的私有实现，从而实现规格的非标准扩展。为了允许应用程序和它使用的实际的 JDBC 2.0 实现隔离，并能够使用这些非标准扩展，JBossJTA 用动态类实例化隐藏了这些私有实现的细节。此外，使用这个机制也不要求使用 JNDI，因为 <interfacename>XADataSource</interfacename> 的实际实现不会被直接地实例化，从而不会把应用程序或驱动捆绑到专门的实现上。因此，JBossJTA 拥有几个用于专有的 JDBC 2.0 实现的类，这些类可以通过设置 <property>dynamicClass</property> 属性在运行时选定："
#. Tag: title
#: JDBC_and_Transactions.xml:166
@@ -651,7 +661,7 @@
"transaction. With the exception of close, all operations performed on the "
"connection at the application level will only be performed on this "
"transaction-specific connection."
-msgstr ""
+msgstr "JBossJTA 连接可以在多个不同的事务里同时使用，例如，在不同的线程里使用和当前事务不同的标记就可能使用相同的 JDBC 连接。JBossJTA 为 JDBC 连接里的每个事务使用连接池。所以，虽然多个线程可能使用相同的 JDBC 连接实例，但在内部可能为每个事务都使用了不同的连接实例。除了关闭操作，连接上的应用程序级别的所有操作都只在该事务专有的连接上进行。"
#. Tag: para
#: JDBC_and_Transactions.xml:232
Modified: labs/jbosstm/enterprise/tags/EAP_4_3_0/Transactions_JTA_Programmers_Guide/zh-CN/Transactions.po
===================================================================
--- labs/jbosstm/enterprise/tags/EAP_4_3_0/Transactions_JTA_Programmers_Guide/zh-CN/Transactions.po 2008-10-29 19:56:54 UTC (rev 23624)
+++ labs/jbosstm/enterprise/tags/EAP_4_3_0/Transactions_JTA_Programmers_Guide/zh-CN/Transactions.po 2008-10-30 01:40:25 UTC (rev 23625)
@@ -1,29 +1,32 @@
+# translation of Transactions.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: Transactions\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-10-30 11:39+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
#: Transactions.xml:6
#, no-c-format
msgid "Transactions"
-msgstr ""
+msgstr "事务"
#. Tag: title
#: Transactions.xml:8
#, no-c-format
msgid "The API"
-msgstr ""
+msgstr "应用程序接口（API ）"
#. Tag: para
#: Transactions.xml:9
@@ -36,7 +39,7 @@
"manager. All of the JTA classes and interfaces occur within the "
"<package>javax.transaction</package> package, and the corresponding JBossJTA "
"implementations within the <package>com.arjuna.ats.jta</package> package."
-msgstr ""
+msgstr "Java Transaction API 由三个元素组成：高级别的应用程序事务限界接口、用于应用服务器的高级别事务管理者接口、用于事务性资源管理者的 X/Open XA 协议的标准 Java 映射。所有 JTA 类和接口都包含在 <package>javax.transaction</package> 包里，而 <package>com.arjuna.ats.jta</package> 包包含相应 JBossJTA 实现。"
#. Tag: para
#: Transactions.xml:13
@@ -50,7 +53,7 @@
"instances. If you do not provide a value, then JBossTS will fabricate one "
"and report the value via the logging infrastructure. The contents of this "
"should be alphanumeric."
-msgstr ""
+msgstr "JBossTS 创建的每个 XID 都必须有唯一的节点标识符，而 JBossTS 将只切换符合指定的节点标识符的事务和状态。这个节点标识符应该通过 <property>com.arjuna.ats.arjuna.xa.nodeIdentifier</property> 属性提供给 JBossTS。你必须确保这个值在 JBossTS 实例中是唯一的。如果你没有提供这个值，JBossTS 将生成一个并在日志里报告这个值。它的内容应该只包含字母和数字。"
#. Tag: title
#: Transactions.xml:18
@@ -345,6 +348,7 @@
#. Tag: para
#: Transactions.xml:133
#, no-c-format
+#, fuzzy
msgid ""
"Transactional resources such as database connections are typically managed "
"by the application server in conjunction with some resource adapter and "
@@ -355,7 +359,7 @@
"enlisted with the transaction so that they can be informed when the "
"transaction terminates, for example, are driven through the two-phase commit "
"protocol."
-msgstr ""
+msgstr "list."
#. Tag: para
#: Transactions.xml:137
@@ -397,6 +401,7 @@
#. Tag: para
#: Transactions.xml:146
#, no-c-format
+#, fuzzy
msgid ""
"The de-list request results in the transaction manager informing the "
"resource manager to end the association of the transaction with the target "
@@ -405,7 +410,7 @@
"resource states must be kept intact. The transaction manager passes the "
"appropriate flag value in its <methodname>XAResource.end</methodname> method "
"call to the underlying resource manager."
-msgstr ""
+msgstr "list<code></code><methodname></methodname>."
#. Tag: title
#: Transactions.xml:150
@@ -470,3 +475,4 @@
" \n"
"boolean isSame = txObj.equals(someOtherTxObj);"
msgstr ""
+
Modified: labs/jbosstm/enterprise/tags/EAP_4_3_0/Transactions_JTA_Programmers_Guide/zh-CN/Using_JBossJTA_in_Application_Servers.po
===================================================================
--- labs/jbosstm/enterprise/tags/EAP_4_3_0/Transactions_JTA_Programmers_Guide/zh-CN/Using_JBossJTA_in_Application_Servers.po 2008-10-29 19:56:54 UTC (rev 23624)
+++ labs/jbosstm/enterprise/tags/EAP_4_3_0/Transactions_JTA_Programmers_Guide/zh-CN/Using_JBossJTA_in_Application_Servers.po 2008-10-30 01:40:25 UTC (rev 23625)
@@ -1,35 +1,38 @@
+# translation of Using_JBossJTA_in_Application_Servers.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: Using_JBossJTA_in_Application_Servers\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-10-30 10:59+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
#: Using_JBossJTA_in_Application_Servers.xml:6
#, no-c-format
msgid "Using JBossJTA in Application Servers"
-msgstr ""
+msgstr "在应用服务器里使用 JBossJTA"
#. Tag: title
#: Using_JBossJTA_in_Application_Servers.xml:8
#, no-c-format
msgid "JBoss Application Server"
-msgstr ""
+msgstr "JBoss 应用服务器"
#. Tag: title
#: Using_JBossJTA_in_Application_Servers.xml:10
#, no-c-format
msgid "Service Configuration"
-msgstr ""
+msgstr "服务配置"
#. Tag: para
#: Using_JBossJTA_in_Application_Servers.xml:11
@@ -38,7 +41,7 @@
"The JBoss Transaction Service is configured primarily via the XML files "
"stored in the etc directory, but when run as a JBOSS service there are a "
"number of configurable attributes available. They are as follows:"
-msgstr ""
+msgstr "JBoss 事务服务主要通过 etc 目录下的 XML 文件进行配置，但它如果作为 JBoss 服务运行，它还可以使用许多可配置属性。例如："
#. Tag: para
#: Using_JBossJTA_in_Application_Servers.xml:17
@@ -46,7 +49,7 @@
msgid ""
"TransactionTimeout – The default transaction timeout to be used for new "
"transactions. Specified as an integer in seconds."
-msgstr ""
+msgstr "TransactionTimeout – 用于新事务的缺省事务超时时间。它是以秒为单位的整型值。"
#. Tag: para
#: Using_JBossJTA_in_Application_Servers.xml:22
@@ -56,7 +59,7 @@
"should gather statistical information. This information can then be viewed "
"using the PerformanceStatistics MBean. Specified as a Boolean. The default "
"is to not gather this information."
-msgstr ""
+msgstr "StatisticsEnabled – 它决定事务服务是否应该收集统计信息。这些信息可以用 PerformanceStatistics MBean 进行查看。它的值为布尔型，缺省为 false，也就是不收集统计信息。"
#. Tag: para
#: Using_JBossJTA_in_Application_Servers.xml:27
@@ -66,7 +69,7 @@
"is propagated by context importer/exporter. If set to false only the current "
"transaction context is propagated. If set to true the full transaction "
"context (including parent transactions) is propagated."
-msgstr ""
+msgstr "PropagateFullContext – 它决定上下文导入者/导出者是否传递完整的事务性上下文。如果为 false，只传递当前的事务性上下文。如果为 true，整个事务上下文（包括父事务）将被传递。"
#. Tag: para
#: Using_JBossJTA_in_Application_Servers.xml:32
@@ -74,7 +77,7 @@
msgid ""
"These attributes are specified as MBean attributes in the jboss-service.xml "
"file located in the server/all/conf directory, for example:"
-msgstr ""
+msgstr "这些属性在 server/all/conf 目录里的 jboss-service.xml 文件里作为 MBean 属性指定，例如："
#. Tag: screen
#: Using_JBossJTA_in_Application_Servers.xml:35
@@ -88,6 +91,13 @@
" \n"
"</mbean>"
msgstr ""
+"<mbean code=\"com.arjuna.ats.jbossatx.jts.TransactionManagerService\" "
+"name=\"jboss:service=TransactionManager\">\n"
+" \n"
+"<attribute name=\"TransactionTimeout\">300</attribute>\n"
+"<attribute name=\"StatisticsEnabled>true</attribute>>\n"
+" \n"
+"</mbean>"
#. Tag: para
#: Using_JBossJTA_in_Application_Servers.xml:36
@@ -96,7 +106,7 @@
"The transaction service is configurable also via the standard JBoss "
"Transaction Service property files. These are located in the JBossTS install "
"location under the etc sub-directory."
-msgstr ""
+msgstr "事务服务也可以通过标准的 JBoss 事务服务属性文件进行配置。这些文件位于 JBossTS 安装目录下的 etc 子目录下。"
#. Tag: para
#: Using_JBossJTA_in_Application_Servers.xml:39
@@ -108,12 +118,14 @@
"to be configured, for example, <code>com.arjuna.ts.properties:module=arjuna</"
"code>."
msgstr ""
+"这些文件可以手工或通过 JMX 进行编辑。每个属性文件都通过名为 <code>com.arjuna.ts.properties</code> 的对象和要配置的模块名称进行开放，如 <code>com.arjuna.ts.properties:module=arjuna</"
+"code>。"
#. Tag: title
#: Using_JBossJTA_in_Application_Servers.xml:43
#, no-c-format
msgid "Logging"
-msgstr ""
+msgstr "日志"
#. Tag: para
#: Using_JBossJTA_in_Application_Servers.xml:44
@@ -130,12 +142,15 @@
"messages. Therefore, these messages will not appear in log files if the "
"filter level is INFO. All other log messages behave as normal."
msgstr ""
+"为了使 JBossTS 日志和 JBossAS 语义上一致，TransactionManagerService 修改了某些日志消息的级别。这是通过覆盖 <filename>jbossjta-properties.xml</"
+"filename> 文件里的 <property>com.arjuna.common.util."
+"logger</property> 属性来实现的。因此，当嵌入地运行在 JBossAS 里时，这个属性的值将不会影响日志行为。通过强制使用 log4j_releveler logger，TransactionManagerService 导致所有 INFO 级别的消息都修改为 DEBUG 级别。因此，如果过滤器级别为 INFO，这些消息不会出现在日志文件里。所有其他日志消息都不受影响。"
#. Tag: title
#: Using_JBossJTA_in_Application_Servers.xml:49
#, no-c-format
msgid "The services"
-msgstr ""
+msgstr "服务"
#. Tag: para
#: Using_JBossJTA_in_Application_Servers.xml:50
@@ -143,7 +158,7 @@
msgid ""
"There is currently one service offered by the JBOSS integration called "
"TransactionManagerService. Here we shall discuss what this service does."
-msgstr ""
+msgstr "JBOSS 集成目前提供一个名为 TransactionManagerService 的服务。下面我们对其进行讨论。"
#. Tag: para
#: Using_JBossJTA_in_Application_Servers.xml:54
@@ -154,13 +169,13 @@
"java:/TransactionManager name with the JNDI provider. This service depends "
"upon the existence of the CORBA ORB Service and it must be using JacORB as "
"the underlying ORB implementation."
-msgstr ""
+msgstr "事务管理者的主要目的是确保启动切换管理者（Recovery Manager）。它也把 JBossTS JTA 事务管理者在 JNDI 提供者里绑定为 java:/TransactionManager。这个服务依赖于 CORBA ORB 服务的扩展，它必须把 JacORB 作为底层的 ORB 实现来使用。"
#. Tag: para
#: Using_JBossJTA_in_Application_Servers.xml:57
#, no-c-format
msgid "There are two instances of this service:"
-msgstr ""
+msgstr "这个服务有两个模式："
#. Tag: para
#: Using_JBossJTA_in_Application_Servers.xml:62
@@ -171,6 +186,8 @@
"use the <classname>com.arjuna.ats.jbossatx.jts.TransactionManagerService</"
"classname> class. This is the default configuration."
msgstr ""
+"distributed：它使用启用 JTS 的事务管理者实现，因此它支持分布式事务和切换。你可以用 <classname>com.arjuna.ats.jbossatx.jts.TransactionManagerService</"
+"classname> 类配置它。这是缺省的模式。"
#. Tag: para
#: Using_JBossJTA_in_Application_Servers.xml:67
@@ -180,12 +197,14 @@
"the <classname>com.arjuna.ats.jbossatx.jta.TransactionManagerService</"
"classname> class."
msgstr ""
+"local：它使用纯本地的 JTA 实现。你可以用 <classname>com.arjuna.ats.jbossatx.jta.TransactionManagerService</"
+"classname> 类配置它。"
#. Tag: title
#: Using_JBossJTA_in_Application_Servers.xml:73
#, no-c-format
msgid "Ensuring Transactional Context is Propagated to the Server"
-msgstr ""
+msgstr "确保事务性上下文被传递到服务器里"
#. Tag: para
#: Using_JBossJTA_in_Application_Servers.xml:74
@@ -197,7 +216,7 @@
"JRMP invocations to the server, the transaction propagation context factory "
"needs to be explicitly set for the JRMP invoker proxy. This is done as "
"follows:"
-msgstr ""
+msgstr "通过 JBoss 服务器外部的协调者协调事务是可能的（如使用外部 OTS 服务器创建的事务）。要确保通过 JRMP 调用把事务上下文传递到服务器里，事务传递上下文工厂需要为 JRMP 调用者代理显性地进行设置。如："
#. Tag: screen
#: Using_JBossJTA_in_Application_Servers.xml:78
@@ -206,3 +225,6 @@
"JRMPInvokerProxy.setTPCFactory( new com.arjuna.ats.internal.jbossatx.jts."
"PropagationContextManager() );"
msgstr ""
+"JRMPInvokerProxy.setTPCFactory( new com.arjuna.ats.internal.jbossatx.jts."
+"PropagationContextManager() );"
+
More information about the jboss-svn-commits
mailing list