[jboss-cvs] JBossAS SVN: r68666 - projects/docs/trunk/Server_Configuration_Guide/zh-CN.
jboss-cvs-commits at lists.jboss.org
jboss-cvs-commits at lists.jboss.org
Mon Jan 7 20:28:43 EST 2008
Author: xhuang at jboss.com
Date: 2008-01-07 20:28:43 -0500 (Mon, 07 Jan 2008)
New Revision: 68666
Modified:
projects/docs/trunk/Server_Configuration_Guide/zh-CN/J2EE_Connectors_On_JBOSS.po
projects/docs/trunk/Server_Configuration_Guide/zh-CN/Transactions.po
Log:
update
Modified: projects/docs/trunk/Server_Configuration_Guide/zh-CN/J2EE_Connectors_On_JBOSS.po
===================================================================
--- projects/docs/trunk/Server_Configuration_Guide/zh-CN/J2EE_Connectors_On_JBOSS.po 2008-01-07 23:50:11 UTC (rev 68665)
+++ projects/docs/trunk/Server_Configuration_Guide/zh-CN/J2EE_Connectors_On_JBOSS.po 2008-01-08 01:28:43 UTC (rev 68666)
@@ -1,30 +1,33 @@
+# translation of J2EE_Connectors_On_JBOSS.po to
# Language /tmp/mike/JBEAP420/JBAS translations for JBEAP package.
-# Copyright (C) 2007 Free Software Foundation, Inc.
+# Copyright (C) 2007, 2008 Free Software Foundation, Inc.
+#
# Automatically generated, 2007.
-#
+# Xi HUANG <xhuang at redhat.com>, 2008.
msgid ""
msgstr ""
-"Project-Id-Version: JBEAP 420\n"
+"Project-Id-Version: J2EE_Connectors_On_JBOSS\n"
"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
"POT-Creation-Date: 2007-12-09 23:23+0000\n"
-"PO-Revision-Date: 2001-02-09 01:25+0100\n"
-"Last-Translator: Automatically generated\n"
-"Language-Team: none\n"
+"PO-Revision-Date: 2008-01-07 14:10+1000\n"
+"Last-Translator: Xi HUANG <xhuang at redhat.com>\n"
+"Language-Team: <zh 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
#: J2EE_Connectors_On_JBOSS.xml:6
#, no-c-format
msgid "Connectors on JBoss"
-msgstr ""
+msgstr "JBoss 连接器"
#. Tag: subtitle
#: J2EE_Connectors_On_JBOSS.xml:7
-#, fuzzy, no-c-format
+#, no-c-format
msgid "The JCA Configuration and Architecture"
-msgstr "JBoss 类加载器架构"
+msgstr "JCA 配置和架构"
#. Tag: para
#: J2EE_Connectors_On_JBOSS.xml:8
@@ -36,13 +39,13 @@
"API standardized access to relational data. The purpose of this chapter is "
"to introduce the utility of the JCA APIs and then describe the architecture "
"of JCA in JBoss"
-msgstr ""
+msgstr "本章讨论了 JBoss 对 J2EE Connector Architecture (JCA) 的实现。JCA 是一个用于资源管理器集成的 API，它的目标是使对非关系型资源的访问和 JDBC API 访问一样标准化。本章的目的是介绍 JCA API 的功能并描述 JBoss 里的 JCA 的架构。"
#. Tag: title
#: J2EE_Connectors_On_JBOSS.xml:12
-#, fuzzy, no-c-format
+#, no-c-format
msgid "JCA Overview"
-msgstr "概况（Overview）"
+msgstr "JCA 概述"
#. Tag: para
#: J2EE_Connectors_On_JBOSS.xml:13
@@ -54,7 +57,7 @@
"of such resource managers as Enterprise Information Systems (EIS). Examples "
"of EIS systems include enterprise resource planning packages, mainframe "
"transaction processing, non-Java legacy applications, etc."
-msgstr ""
+msgstr "J2EE 1.4 包含连接器架构（JCA）规格，它允许把事务性和安全资源适配器集成到 J2EE 应用程序服务器环境里。JCA 规格以 Enterprise Information Systems (EIS) 来描述这些资源管理者。EIS 系统的例子包括企业资源规划软件包、大型机事务处理、非 Java 应用程序等等。"
#. Tag: para
#: J2EE_Connectors_On_JBOSS.xml:16
@@ -66,7 +69,7 @@
"to integrate into JBoss in a secure, scalable and transacted manner. In this "
"introduction we will focus on resource adapters as a generic notion rather "
"than something specific to the EIS environment."
-msgstr ""
+msgstr "注重 EIS 的原因主要是事务、安全性和伸缩性是对企业级软件系统的要求。然而，JCA 适用于任何需要以安全、可伸缩和事务性的方式集成到 JBoss 里的资源。本章我们将着重于通用的资源适配器而不是特定 EIS 环境。"
#. Tag: para
#: J2EE_Connectors_On_JBOSS.xml:19
@@ -77,7 +80,7 @@
"management facilities of an application server with those of a resource "
"manager. The SPI defines the system level contract between the resource "
"adaptor and the application server."
-msgstr ""
+msgstr "连接器架构为应用服务器的事务、安全性和连接管理功能和资源管理者的集成定义了标准的 SPI（服务提供者接口）。这个 SPI 定义资源适配器和应用服务器间的系统级协议。"
#. Tag: para
#: J2EE_Connectors_On_JBOSS.xml:22
@@ -92,7 +95,7 @@
"a type specific API. To be used effectively it must be used in conjunction "
"with metadata that describes how to map from the generic CCI API to the "
"resource manager specific data types used internally by the resource manager."
-msgstr ""
+msgstr "连接器架构也定义用于访问资源的通用客户接口（CCI，Common Client Interface）。这个 CCI 以 EIS 开发工具和其他复杂集成资源的用户为目标。它提供了一个将这些工具所需的 EIS 代码最小化的途径。J2EE 开发人员通常将通过这样的工具或和资源相关的接口而不是直接使用 CCI 访问资源。其原因是 CCI 并非和类型相关的 API。要有效地使用它，它必须和描述从通用 CCI API 映射到资源管理者内部使用的数据类型的元数据一起使用。"
#. Tag: para
#: J2EE_Connectors_On_JBOSS.xml:25
@@ -106,7 +109,7 @@
"enterprise application. A resource vendor need only implement a JCA "
"compliant adaptor once to allow use of the resource manager in any JCA "
"capable application server."
-msgstr ""
+msgstr "连接器架构的目的是让资源供应商为其产品提供标准的适配器。资源适配器是 Java 应用程序用来连接资源的系统级的软件驱动。资源适配器插入应用服务器来提供资源管理者、应用服务器和企业级应用程序间的连接。资源供应商只需要部署一次兼容 JCA 的适配器，就可以在任何具有 JCA 功能的应用服务器里使用资源管理者。"
#. Tag: para
#: J2EE_Connectors_On_JBOSS.xml:28
@@ -117,14 +120,13 @@
"multiple resource managers. Likewise, a resource manager vendor provides one "
"standard resource adaptor and it has the capability to plug in to any "
"application server that supports the connector architecture."
-msgstr ""
+msgstr "应用服务器供应商扩展其架构来支持连接者架构来保证多个资源管理者间的无缝连接。类似地，资源管理者供应商提供标准的适配器且它具有插入到任何支持连接者构建的应用服务器里的能力。"
#. Tag: title
#: J2EE_Connectors_On_JBOSS.xml:32
#, no-c-format
-msgid ""
-"The relationship between a J2EE application server and a JCA resource adaptor"
-msgstr ""
+msgid "The relationship between a J2EE application server and a JCA resource adaptor"
+msgstr "J2EE 应用服务器和 JCA 资源适配器之间的关系"
#. Tag: para
#: J2EE_Connectors_On_JBOSS.xml:39
@@ -134,7 +136,7 @@
"the JCA SPI to allow a resource adaptor to integrate with the server "
"connection pooling, transaction management and security management "
"facilities. This integration API defines a three-part system contract."
-msgstr ""
+msgstr "解释了应用服务器提供对 JCA SPI 的支持，它允许资源适配器和服务器连接池、事务管理和安全管理功能的集成。这种集成 API 定义了一个 3 部分的系统协议。"
#. Tag: para
#: J2EE_Connectors_On_JBOSS.xml:44
@@ -145,26 +147,24 @@
"the pool management is to allow for scalability. Resource connections are "
"typically expense objects to create and pooling them allows for more "
"effective reuse and management."
-msgstr ""
+msgstr "<emphasis role=\"bold\">连接管理（Connection management）</emphasis>：允许应用服务器为资源连接设立缓冲池。池管理的目的是允许伸缩性。创建资源连接对象通常开销较大，设立缓冲池可以更有效的重用和管理。"
#. Tag: para
#: J2EE_Connectors_On_JBOSS.xml:49
-#, fuzzy, no-c-format
+#, no-c-format
msgid ""
"<emphasis role=\"bold\">Transaction Management</emphasis>: a contract that "
"allows the application server transaction manager to manage transactions "
"that engage resource managers."
-msgstr ""
-"<emphasis role=\"bold\">TransactionManagerService</emphasis>：JTA 事务管理服"
-"务的 JMX ObjectName。"
+msgstr "<emphasis role=\"bold\">（事务管理）Transaction Management</emphasis>：这是允许应用服务器事务管理者管理和资源管理者相关的事务的协议。"
#. Tag: para
#: J2EE_Connectors_On_JBOSS.xml:54
-#, fuzzy, no-c-format
+#, no-c-format
msgid ""
"<emphasis role=\"bold\">Security Management</emphasis>: a contract that "
"enables secured access to resource managers."
-msgstr "<emphasis role=\"bold\">Instrumentation</emphasis> 它是所管理的资源"
+msgstr "<emphasis role=\"bold\">安全管理（Security Management）</emphasis>：启用对资源管理者的安全访问的协议。"
#. Tag: para
#: J2EE_Connectors_On_JBOSS.xml:59
@@ -176,7 +176,7 @@
"integration information. The resource adaptor also exposes the resource "
"manager to the application server components. This can be done using the CCI "
"and/or a resource adaptor specific API."
-msgstr ""
+msgstr "资源适配器实现了系统协议的资源管理者方面。这有必要利用应用服务器连接池、提供事务资源信息和安全性集成信息。资源适配器也为应用服务器组件开放资源管理者。这可以用 CCI 和/或资源适配器相关的 API 来实现。"
#. Tag: para
#: J2EE_Connectors_On_JBOSS.xml:62
@@ -191,6 +191,8 @@
"resource adaptor is that the client has the option of using the resource "
"adaptor independent CCI API if the resource adaptor supports this."
msgstr ""
+"应用程序组件用标准的 J2EE 容器和组件间的协议集成到应用服务器里。对于 EJB 组件，这个协议由 规格定义。应用程序组件和资源适配器的交互和与其他标准资源工厂一样（例如，<literal>javax.sql."
+"DataSource</literal> JDBC 资源工厂）。唯一的区别是客户可以选择独立于资源适配器的 CCI API（如果支持的话）。"
#. Tag: para
#: J2EE_Connectors_On_JBOSS.xml:65
@@ -199,7 +201,7 @@
"(from the JCA 1.5 specification) illustrates the relationship between the "
"JCA architecture participants in terms of how they relate to the JCA SPI, "
"CCI and JTA packages."
-msgstr ""
+msgstr "（JCA 1.5 规格）根据和 JCA SPI、CCI 和 JTA 软件包的关联，解释了 JCA 架构参与者之间的关系。"
#. Tag: title
#: J2EE_Connectors_On_JBOSS.xml:69
@@ -207,7 +209,7 @@
msgid ""
"The JCA 1.0 specification class diagram for the connection management "
"architecture."
-msgstr ""
+msgstr "JCA 1.0 规格用于连接管理架构的类图。"
#. Tag: para
#: J2EE_Connectors_On_JBOSS.xml:76
@@ -222,12 +224,17 @@
"implementation are discussed in the following section on the JBossCX "
"architecture."
msgstr ""
+"JBossCX 架构提供了对应用服务器相关的类的实现。<xref linkend=\"JCA_Overview-"
+"The_JCA_1.0_specification_class_diagram_for_the_connection_management_architecture."
+"\"/> 演示了对 <literal>javax."
+"resource.spi.ConnectionManager</literal> 和 <literal>javax.resource.spi."
+"ConnectionEventListener</literal> 接口的实现。这种实现的关键内容将在 JBossCX 架构的后续章节里进行讨论。"
#. Tag: title
#: J2EE_Connectors_On_JBOSS.xml:82
-#, fuzzy, no-c-format
+#, no-c-format
msgid "An Overview of the JBossCX Architecture"
-msgstr "JBossNS 架构"
+msgstr "JBossCX 架构概述"
#. Tag: para
#: J2EE_Connectors_On_JBOSS.xml:83
@@ -237,7 +244,7 @@
"required for the use of JCA resource adaptors. This is primarily a "
"connection pooling and management extension along with a number of MBeans "
"for loading resource adaptors into the JBoss server."
-msgstr ""
+msgstr "JBossCX 框架提供了使用 JCA 资源适配器所需的应用服务器架构扩展。这主要是一个连接池和管理扩展以及一些将资源适配器加载到 JBoss 服务器里的 MBean。"
#. Tag: para
#: J2EE_Connectors_On_JBOSS.xml:86
@@ -253,6 +260,10 @@
"available to the <literal>org.jboss.resource.connectionmanager."
"RARDeployment</literal> MBean."
msgstr ""
+"组成 RAR 部署的有 3 对 MBean。它们是 <literal>org.jboss.resource.deployment.RARDeployment</literal>、<literal>org."
+"jboss.resource.connectionmanager.RARDeployment</literal> 和 <literal>org."
+"jboss.resource.connectionmanager.BaseConnectionManager2</literal>。<literal>org.jboss.resource.deployment.RARDeployment</literal> 只是 RAR <literal>META-INF/ra.xml</literal> 描述符的元数据的封装。它以 DynamicMBean 简单地开放这些信息使之为 <literal>org.jboss.resource.connectionmanager."
+"RARDeployment</literal> MBean 所用。"
#. Tag: para
#: J2EE_Connectors_On_JBOSS.xml:89
@@ -269,12 +280,16 @@
"implementation with a <literal>org.jboss.resource.connectionmgr."
"RARDeployment</literal> dependent."
msgstr ""
+"RARDeployer 服务处理包含资源适配器（RAR）的归档文件的部署。当 RAR 被部署时，它创建 <literal>org.jboss.resource."
+"deployment.RARDeployment</literal> MBean。部署 RAR 文件是使资源适配器为应用程序组件所用的第一步。对于每个被部署的 RAR，必须配置一个或多个连接工厂并绑定到 JNDI。这个任务由设立依赖 <literal>org.jboss.resource.connectionmgr."
+"RARDeployment</literal> 的 <literal>org.jboss."
+"resource.connectionmanager.BaseConnectionManager2</literal> MBean 的 JBoss 服务描述符来完成。"
#. Tag: title
#: J2EE_Connectors_On_JBOSS.xml:93
#, no-c-format
msgid "BaseConnectionManager2 MBean"
-msgstr ""
+msgstr "BaseConnectionManager2 MBean"
#. Tag: para
#: J2EE_Connectors_On_JBOSS.xml:94
@@ -294,8 +309,7 @@
#. Tag: para
#: J2EE_Connectors_On_JBOSS.xml:97
#, no-c-format
-msgid ""
-"The common attributes supported by the BaseConnectionManager2 MBean are:"
+msgid "The common attributes supported by the BaseConnectionManager2 MBean are:"
msgstr ""
#. Tag: para
@@ -358,9 +372,9 @@
#. Tag: title
#: J2EE_Connectors_On_JBOSS.xml:125
-#, fuzzy, no-c-format
+#, no-c-format
msgid "RARDeployment MBean"
-msgstr "The SARDeployer MBean"
+msgstr "RARDeployment MBean"
#. Tag: para
#: J2EE_Connectors_On_JBOSS.xml:126
@@ -421,6 +435,21 @@
" ...\n"
"</properties>"
msgstr ""
+"<properties>\n"
+" <config-property>\n"
+" <config-property-name>Attr0Name</config-property-name>\n"
+" <config-property-type>Attr0Type</config-property-type>\n"
+" <config-property-value>Attr0Value</config-property-"
+"value>\n"
+" </config-property>\n"
+" <config-property>\n"
+" <config-property-name>Attr1Name</config-property-name>\n"
+" <config-property-type>Attr2Type</config-property-type>\n"
+" <config-property-value>Attr2Value</config-property-"
+"value>\n"
+" </config-property> \n"
+" ...\n"
+"</properties>"
#. Tag: para
#: J2EE_Connectors_On_JBOSS.xml:140
@@ -453,7 +482,7 @@
#: J2EE_Connectors_On_JBOSS.xml:153
#, no-c-format
msgid "JBossManagedConnectionPool MBean"
-msgstr ""
+msgstr "JBossManagedConnectionPool MBean"
#. Tag: para
#: J2EE_Connectors_On_JBOSS.xml:154
@@ -699,9 +728,9 @@
#. Tag: programlisting
#: J2EE_Connectors_On_JBOSS.xml:264
-#, fuzzy, no-c-format
+#, no-c-format
msgid "[examples]$ ant -Dchap=jca build-chap"
-msgstr "[examples]$ ant -Dchap=chap2 -Dex=3 run-example"
+msgstr "[examples]$ ant -Dchap=jca build-chap"
#. Tag: para
#: J2EE_Connectors_On_JBOSS.xml:265
@@ -717,8 +746,7 @@
#. Tag: title
#: J2EE_Connectors_On_JBOSS.xml:268
#, no-c-format
-msgid ""
-"The nontransactional file system resource adaptor deployment descriptor."
+msgid "The nontransactional file system resource adaptor deployment descriptor."
msgstr ""
#. Tag: programlisting
@@ -803,6 +831,83 @@
" </resourceadapter>\n"
"</connector>"
msgstr ""
+"<?xml version=\"1.0\" encoding=\"UTF-8\"?>\n"
+"<connector xmlns=\"http://java.sun.com/xml/ns/\"Whats_new_in_JBoss_4-"
+"J2EE_Certification_and_Standards_Compliance\"\n"
+" xmlns:xsi=\"http://www.w3.org/2001/XMLSchema-instance\"\n"
+" xsi:schemaLocation=\"http://java.sun.com/xml/ns/j2ee \n"
+" http://java.sun.com/xml/ns/j2ee/connector_1_5.xsd\" "
+"version=\"1.5\">\n"
+" <display-name>File System Adapter</display-name>\n"
+" <vendor-name>JBoss</vendor-name>\n"
+" <eis-type>FileSystem</eis-type>\n"
+" <resourceadapter-version>1.0</resourceadapter-version>\n"
+" <license>\n"
+" <description>LGPL</description>\n"
+" <license-required>false</license-required>\n"
+" </license>\n"
+" <resourceadapter>\n"
+" <resourceadapter-class>\n"
+" org.jboss.resource.deployment.DummyResourceAdapter\n"
+" </resourceadapter-class>\n"
+" <outbound-resourceadapter>\n"
+" <connection-definition>\n"
+" <emphasis role=\"bold\"><managedconnectionfactory-"
+"class> org.jboss.book.jca.ex1.ra.FSManagedConnectionFactory </"
+"managedconnectionfactory-class></emphasis>\n"
+" <config-property>\n"
+" <config-property-name>FileSystemRootDir</config-"
+"property-name>\n"
+" <config-property-type>java.lang.String</config-"
+"property-type>\n"
+" <config-property-value>/tmp/db/fs_store</config-"
+"property-value>\n"
+" </config-property>\n"
+" <config-property>\n"
+" <config-property-name>UserName</config-property-"
+"name>\n"
+" <config-property-type>java.lang.String</config-"
+"property-type>\n"
+" <config-property-value/>\n"
+" </config-property>\n"
+" <config-property>\n"
+" <config-property-name>Password</config-property-"
+"name>\n"
+" <config-property-type>java.lang.String</config-"
+"property-type>\n"
+" <config-property-value/>\n"
+" </config-property>\n"
+" <emphasis role=\"bold\"><connectionfactory-interface> "
+"org.jboss.book.jca.ex1.ra.DirContextFactory </connectionfactory-"
+"interface> <connectionfactory-impl-class> org.jboss.book.jca.ex1.ra."
+"DirContextFactoryImpl </connectionfactory-impl-class> <connection-"
+"interface> javax.naming.directory.DirContext </connection-"
+"interface> <connection-impl-class> org.jboss.book.jca.ex1.ra."
+"FSDirContext </connection-impl-class></emphasis>\n"
+" </connection-definition>\n"
+" <transaction-support>NoTransaction</transaction-"
+"support>\n"
+" <authentication-mechanism>\n"
+" <authentication-mechanism-type>BasicPassword</"
+"authentication-mechanism-type>\n"
+" <credential-interface>\n"
+" javax.resource.spi.security.PasswordCredential\n"
+" </credential-interface>\n"
+" </authentication-mechanism>\n"
+" <emphasis role=\"bold\"><reauthentication-support>true</"
+"reauthentication-support></emphasis>\n"
+" </outbound-resourceadapter>\n"
+" <security-permission>\n"
+" <description> Read/Write access is required to the "
+"contents of the\n"
+" FileSystemRootDir </description>\n"
+" <security-permission-spec> permission java.io."
+"FilePermission\n"
+" \"/tmp/db/fs_store/*\", \"read,write\"; \n"
+" </security-permission-spec>\n"
+" </security-permission>\n"
+" </resourceadapter>\n"
+"</connector>"
#. Tag: para
#: J2EE_Connectors_On_JBOSS.xml:270
@@ -928,6 +1033,25 @@
" </no-tx-connection-factory>\n"
"</connection-factories>"
msgstr ""
+"<!DOCTYPE connection-factories PUBLIC\n"
+" \"-//JBoss//DTD JBOSS JCA Config 1.5//EN\"\n"
+" \"http://www.jboss.org/j2ee/dtd/jboss-ds_1_5.dtd\">\n"
+"<!-- \n"
+" The non-transaction FileSystem resource adaptor service "
+"configuration\n"
+"-->\n"
+"<connection-factories>\n"
+" <no-tx-connection-factory>\n"
+" <jndi-name>NoTransFS</jndi-name>\n"
+" <rar-name>jca-ex1.rar</rar-name>\n"
+" <connection-definition>\n"
+" org.jboss.book.jca.ex1.ra.DirContextFactory\n"
+" </connection-definition>\n"
+" <config-property name=\"FileSystemRootDir\"\n"
+" type=\"java.lang.String\">/tmp/db/fs_store</"
+"config-property>\n"
+" </no-tx-connection-factory>\n"
+"</connection-factories>"
#. Tag: para
#: J2EE_Connectors_On_JBOSS.xml:310
@@ -1701,8 +1825,7 @@
msgid ""
"Elements in common to the <literal>local-tx-datasource</literal> and "
"<literal>xa-datasource</literal> are:"
-msgstr ""
-"在 <literal>Order</literal> 中，<literal>OrderLine</literal> 的集合则是这样："
+msgstr "在 <literal>Order</literal> 中，<literal>OrderLine</literal> 的集合则是这样："
#. Tag: para
#: J2EE_Connectors_On_JBOSS.xml:673
@@ -1838,8 +1961,7 @@
msgid ""
"The failover options common to <literal>ha-xa-datasource</literal> and "
"<literal>ha-local-tx-datasource</literal> are:"
-msgstr ""
-"在 <literal>Order</literal> 中，<literal>OrderLine</literal> 的集合则是这样："
+msgstr "在 <literal>Order</literal> 中，<literal>OrderLine</literal> 的集合则是这样："
#. Tag: para
#: J2EE_Connectors_On_JBOSS.xml:743
@@ -2240,3 +2362,4 @@
"true property type using the associated type <literal>PropertyEditor</"
"literal>."
msgstr ""
+
Modified: projects/docs/trunk/Server_Configuration_Guide/zh-CN/Transactions.po
===================================================================
--- projects/docs/trunk/Server_Configuration_Guide/zh-CN/Transactions.po 2008-01-07 23:50:11 UTC (rev 68665)
+++ projects/docs/trunk/Server_Configuration_Guide/zh-CN/Transactions.po 2008-01-08 01:28:43 UTC (rev 68666)
@@ -1,30 +1,33 @@
+# translation of Transactions.po to
# Language /tmp/mike/JBEAP420/JBAS translations for JBEAP package.
-# Copyright (C) 2007 Free Software Foundation, Inc.
-# Automatically generated, 2007.
+# Copyright (C) 2007, 2008 Free Software Foundation, Inc.
#
+# Automatically generated, 2007.
+# Xi HUANG <xhuang at redhat.com>, 2008.
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: 2007-12-09 23:23+0000\n"
-"PO-Revision-Date: 2001-02-09 01:25+0100\n"
-"Last-Translator: Automatically generated\n"
-"Language-Team: none\n"
+"PO-Revision-Date: 2008-01-08 11:28+1000\n"
+"Last-Translator: Xi HUANG <xhuang at redhat.com>\n"
+"Language-Team: <zh 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 "JTA TransactionManagers"
+msgstr "JTA 事务服务"
#. Tag: para
#: Transactions.xml:8
@@ -41,6 +44,8 @@
"transactions. For distributed transaction support the JTS version of JBoss "
"Transactions will need to be used."
msgstr ""
+"本章讨论 JBoss 和 JBossTX 架构里的事务管理。JBossTX 架构允许使用任何 Java Transaction API "
+"(JTA) 事务管理者的实现。JBossTX 包括一个快速的 VM 内的 JTA 实现（现在已被取消）。JBoss Transactions (JBoss TS) 是 JBoss 的新的缺省事务管理者。JBoss TS 建立在成熟的分布式事务技术上。JBoss 服务器带有的 JBoss Transactions 的 JTA 版本提供完全可恢复事务的支持。对于分布式事务的支持，必须使用其 JTS 版本。"
#. Tag: para
#: Transactions.xml:11
@@ -51,13 +56,13 @@
"architecture discussion. We will then discuss the interfaces that make up "
"the JBossTX architecture and conclude with a discussion of the MBeans "
"available for integration of alternate transaction managers."
-msgstr ""
+msgstr "我们将首先提供对事务和 JTA 的关键概念的概述，这将为讨论 JBossTX 架构打下良好的基础。然后我们将讨论组成 JBossTX 架构的接口以及集成其他事务管理者的可用 MBean。"
#. Tag: title
#: Transactions.xml:15
-#, fuzzy, no-c-format
+#, no-c-format
msgid "Transaction/JTA Overview"
-msgstr "事务超时"
+msgstr "事务/JTA 概述"
#. Tag: para
#: Transactions.xml:16
@@ -68,7 +73,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 是事务的 4 个重要属性：原子性、一致性、隔离性和持久性的首字母组合。这些术语的意思是："
#. Tag: para
#: Transactions.xml:21
@@ -78,17 +83,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\">Atomicity</emphasis>：事务必须是原子的。这表示要么事务里的所有任务都被执行，要么都不执行。只完成一部分事务是不允许的。"
#. Tag: para
#: Transactions.xml:26
-#, 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\">Consistency</emphasis>：当事务被完成时，系统必须处于稳定和一致的状态。"
#. Tag: para
#: Transactions.xml:31
@@ -99,7 +102,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\">Isolation</emphasis>：不同的事务必须相互隔离。这表示一个事务完成的部分工作在事务提交前对于其他事务是不可见的，且通过编程，多用户系统里的每个进程都好像是访问该系统的唯一进程。"
#. Tag: para
#: Transactions.xml:36
@@ -109,7 +112,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\">Durability</emphasis>：事务提交后，事务期间的修改被持久化。当事务被提交后，即使之后服务器崩溃，其修改也不会丢失。"
#. Tag: para
#: Transactions.xml:41
@@ -121,7 +124,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。金额为 M 从帐号 A 移至帐号 B，可以从帐号 A 里减去 M 并在帐号 B 里增加 M。这个操作必须在一个事务里完成，所有的 4 个 ACID 属性都很重要。"
#. Tag: para
#: Transactions.xml:44
@@ -130,7 +133,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 "atomicity 属性表示支取和存入都作为不可分割的单元执行。如果由于某种原因两者不能都完成的话，那两者都不会执行。"
#. Tag: para
#: Transactions.xml:47
@@ -138,7 +141,7 @@
msgid ""
"The consistency property means that after the transaction, the sum of the "
"amounts of all accounts must still be 0."
-msgstr ""
+msgstr "consistency 属性表示在该交易后，所有帐号的金额总和必须仍旧为 0。"
#. Tag: para
#: Transactions.xml:50
@@ -153,7 +156,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 "如果有多个银行职员同时使用这个系统时，isolation 属性就很重要。支取或存入可以用 3 步来实现：首先，从数据库里读取该帐号的金额；然后减去或增加某个数额；最后把新的金额写入数据库。如果不使用事务，一些情况就可能会发生。例如，如果两人同时读取了帐号 A 的金额，然后各自增加或减去某个数额并写入数据库，第一个修改就有可能错误地被最后的修改所覆盖。"
#. Tag: para
#: Transactions.xml:53
@@ -162,13 +165,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 "durability 属性也很重要。如果某笔转帐交易被启动，银行必须相信随后的某些故障将不能够撤销该笔交易。"
#. Tag: title
#: Transactions.xml:57
-#, fuzzy, no-c-format
+#, no-c-format
msgid "Pessimistic and optimistic locking"
-msgstr "悲观锁定（Pessimistic Locking）"
+msgstr "悲观和乐观锁定"
#. Tag: para
#: Transactions.xml:58
@@ -177,7 +180,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:61
@@ -195,7 +198,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 "悲观锁定的劣势是从事务里第一次开始访问时资源就被锁定，直到事务结束，这个期间它不能被其他事务访问。如果大多数事务都只是简单地查看资源而不进行修改，使用排它型锁（exclusive lock）就太过分了，因为这会导致锁的争用，此时乐观锁定可能是一个更好的选择。悲观锁定是一种故障保险的方法。在银行程序示例里，只要在事务里被访问，帐号就被锁定。此时如果在其他事务里试图使用这个帐号，将导致其他进程被延迟，直到帐号解锁；或者导致该事务被回滚。事务被提交或回滚后这个锁才会被释放。"
#. Tag: para
#: Transactions.xml:64
@@ -211,7 +214,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:67
@@ -223,13 +226,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 "在 banking 示例里，当帐号第一次在事务里被访问时，其金额将保存起来。如果事务修改了这个j金额的值，在更新金额前将读取保存的金额值。如果在事务开始后其值有变化，事务将使自己失效，否则新的金额将写入到持久存储设备里。"
#. Tag: title
#: Transactions.xml:73
#, no-c-format
msgid "The components of a distributed transaction"
-msgstr ""
+msgstr "分布式事务的组件"
#. Tag: para
#: Transactions.xml:74
@@ -237,7 +240,7 @@
msgid ""
"There are a number of participants in a distributed transaction. These "
"include:"
-msgstr ""
+msgstr "在分布式事务里有一些参与者。它们包括："
#. Tag: para
#: Transactions.xml:79
@@ -247,7 +250,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:84
@@ -256,7 +259,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:89
@@ -268,7 +271,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>：事务性客户可以调用单个事务里的一个或多个事务性对象的操作。启动事务的事务性客户被称为事务始发者（transaction originator）。事务性客户是 JTA 接口的显性或隐形用户，它在 JTA 里没有接口。"
#. Tag: para
#: Transactions.xml:94
@@ -278,7 +281,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>：事务性对象是其行为被事务性上下文里执行的操作所影响的对象。事务性对象也可以是一个事务性客户。多数 Enterprise Java Bean 是事务性对象。"
#. Tag: para
#: Transactions.xml:99
@@ -295,13 +298,13 @@
"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:107
#, no-c-format
msgid "The two-phase XA protocol"
-msgstr ""
+msgstr "两阶段的 XA 协议"
#. Tag: para
#: Transactions.xml:108
@@ -312,7 +315,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:111
@@ -415,9 +418,9 @@
#. Tag: title
#: Transactions.xml:139
-#, fuzzy, no-c-format
+#, no-c-format
msgid "Transaction IDs and branches"
-msgstr "事务和并发"
+msgstr "事务 ID 和分支"
#. Tag: para
#: Transactions.xml:140
@@ -447,8 +450,7 @@
#. Tag: para
#: Transactions.xml:155
#, 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
@@ -508,22 +510,19 @@
#. Tag: para
#: Transactions.xml:186
#, 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:191
#, 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:196
#, 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
@@ -551,8 +550,7 @@
#. Tag: para
#: Transactions.xml:216
#, 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
@@ -571,9 +569,9 @@
#. Tag: title
#: Transactions.xml:227
-#, fuzzy, no-c-format
+#, no-c-format
msgid "Configuring JBoss Transactions"
-msgstr "JTA TransactionManagers"
+msgstr "配置 JBoss 事务"
#. Tag: para
#: Transactions.xml:228
@@ -605,54 +603,3 @@
"SOAP/HTTP."
msgstr ""
-#, fuzzy
-#~ msgid "Adapting a Transaction Manager to JBoss"
-#~ msgstr "JTA TransactionManagers"
-
-#, fuzzy
-#~ msgid "The Default Transaction Manager"
-#~ msgstr "JTA TransactionManagers"
-
-#, fuzzy
-#~ msgid ""
-#~ "<emphasis role=\"bold\">TransactionTimeout</emphasis>: The default "
-#~ "transaction timeout in seconds. The default value is 300 seconds (5 "
-#~ "minutes)."
-#~ msgstr ""
-#~ "<emphasis role=\"bold\">jnp.discoveryTimeout</emphasis>：等待发现查询的应"
-#~ "答的毫秒数。缺省值为 5000(5 秒)。"
-
-#, fuzzy
-#~ msgid ""
-#~ "<emphasis role=\"bold\">InterruptThreads</emphasis>: Indicates whether or "
-#~ "not the transaction manager should interrupt threads when the transaction "
-#~ "times out. The default value is false."
-#~ msgstr ""
-#~ "<emphasis role=\"bold\">NumAcceptThreads</emphasis>：用来接受客户联接的线"
-#~ "程的数量。它的缺省值是 1。"
-
-#, fuzzy
-#~ msgid ""
-#~ "<emphasis role=\"bold\">GlobalIdsEnabled</emphasis>: Indicates whether or "
-#~ "not the transaction manager should use global transaction ids. This "
-#~ "should be set to true for transaction demarcation over IIOP. The default "
-#~ "value is true."
-#~ msgstr ""
-#~ "<emphasis role=\"bold\">NumAcceptThreads</emphasis>：用来接受客户联接的线"
-#~ "程的数量。它的缺省值是 1。"
-
-#, fuzzy
-#~ msgid "org.jboss.tm.XidFactory"
-#~ msgstr "The org.jboss.naming.NamingContextFactory"
-
-#, fuzzy
-#~ msgid ""
-#~ "<emphasis role=\"bold\">GlobalIdNumber</emphasis>: A long value used as "
-#~ "initial transaction id. The default is 0."
-#~ msgstr ""
-#~ "<emphasis role=\"bold\">Backlog</emphasis>：与服务器接受套接字关联的 "
-#~ "backlog。缺省值是 200。"
-
-#, fuzzy
-#~ msgid "UserTransaction Support"
-#~ msgstr "jta.UserTransaction"
More information about the jboss-cvs-commits
mailing list