[jboss-cvs] JBossAS SVN: r75682 - projects/docs/enterprise/4.3/Messaging/JBoss_Messaging_User_Guide/zh-CN.
jboss-cvs-commits at lists.jboss.org
jboss-cvs-commits at lists.jboss.org
Fri Jul 11 08:19:04 EDT 2008
Author: xhuang at jboss.com
Date: 2008-07-11 08:19:04 -0400 (Fri, 11 Jul 2008)
New Revision: 75682
Modified:
projects/docs/enterprise/4.3/Messaging/JBoss_Messaging_User_Guide/zh-CN/Configuration.po
projects/docs/enterprise/4.3/Messaging/JBoss_Messaging_User_Guide/zh-CN/Important_Features.po
Log:
update
Modified: projects/docs/enterprise/4.3/Messaging/JBoss_Messaging_User_Guide/zh-CN/Configuration.po
===================================================================
--- projects/docs/enterprise/4.3/Messaging/JBoss_Messaging_User_Guide/zh-CN/Configuration.po 2008-07-11 12:09:42 UTC (rev 75681)
+++ projects/docs/enterprise/4.3/Messaging/JBoss_Messaging_User_Guide/zh-CN/Configuration.po 2008-07-11 12:19:04 UTC (rev 75682)
@@ -1,23 +1,26 @@
# Language zh-CN translations for JBoss_Messaging_User_Guide package.
# Copyright (C) 2008 Free Software Foundation, Inc.
+#
# Automatically generated, 2008.
-#
+# Xi HUANG <xhuang at redhat.com>, 2008.
msgid ""
msgstr ""
"Project-Id-Version: JBoss_Messaging_User_Guide 4.3\n"
"POT-Creation-Date: 2001-02-09 01:25+0100\n"
-"PO-Revision-Date: 2001-02-09 01:25+0100\n"
-"Last-Translator: Automatically generated\n"
-"Language-Team: none\n"
+"PO-Revision-Date: 2008-07-11 22:18+1000\n"
+"Last-Translator: Xi HUANG <xhuang at redhat.com>\n"
+"Language-Team: Chinese Simplified <kde-i18n-doc at lists.kde.org>\n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=UTF-8\n"
"Content-Transfer-Encoding: 8bit\n"
+"X-Generator: KAider 0.1\n"
+"Plural-Forms: nplurals=2; plural=n != 1;\n"
#. Tag: title
#: Configuration.xml:3
#, no-c-format
msgid "Configuration"
-msgstr ""
+msgstr "配置"
#. Tag: para
#: Configuration.xml:4
@@ -33,6 +36,9 @@
"JBoss Messaging, which work together to provide JMS API level services to "
"client applications."
msgstr ""
+"JMS API 指定消息客户端怎样和服务器进行交互。消息服务的确切定义和实现，如消息目的地和连接工厂，都是 JMS 提供者所专有的。JBoss "
+"Messaging 具有自己的配置文件来对服务进行配置。如果你准备从 JBossMQ（或其他 JMS 提供者）移植服务到 JBoss Messaging "
+"里，你需要理解这些配置文件。在本章我们将讨论如何配置 JBoss Messaging 里的不同服务，使其为客户应用程序提供 JMS API 级的服务。"
#. Tag: para
#: Configuration.xml:13
@@ -46,6 +52,11 @@
"the name of your database)</filename>, <filename>connection-factories-"
"service.xml</filename> and <filename>destinations-service.xml</filename>."
msgstr ""
+"JBoss Messaging 服务的配置分布在几个配置文件里。根据所配置服务的功能，配置数据分布在 <filename>"
+"messaging-service.xml</filename>、<filename>remoting-bisocket-service.xml<"
+"/filename>、 <filename>xxx-persistence-service.xml（这里的 xxx 是数据库名）</filename>"
+"、<filename>connection-factories-service.xml</filename> 和 <filename>"
+"destinations-service.xml</filename> 里。"
#. Tag: para
#: Configuration.xml:21
@@ -58,12 +69,16 @@
"you don't need them. Be very careful you have considered the security "
"implications before removing the security interceptor."
msgstr ""
+"AOP 客户端和服务器端的拦截器栈在 <filename>aop-messaging-client.xml</filename> 和 <filename>"
+"aop-messaging-server.xml</filename> "
+"里进行配置。通常你不用改动它们，但你可以删除某些不需要的拦截器来小幅提高性能。在删除安全拦截器（security "
+"interceptor）之前，请先仔细考虑安全隐患。"
#. Tag: title
#: Configuration.xml:29
#, no-c-format
msgid "Configuring the ServerPeer"
-msgstr ""
+msgstr "配置 ServerPeer"
#. Tag: para
#: Configuration.xml:30
@@ -73,12 +88,14 @@
"configuration, resides in <filename>messaging-service.xml</filename> "
"configuration file."
msgstr ""
+"Server Peer 是 JBoss Messaging JMS facade 的核心。相关服务器的配置位于 <filename>"
+"messaging-service.xml</filename> 文件里。"
#. Tag: para
#: Configuration.xml:33
#, no-c-format
msgid "All JBoss Messaging services are rooted at the server peer."
-msgstr ""
+msgstr "所有的 JBoss Messaging 服务在 server peer 里都以根用户运行。"
#. Tag: para
#: Configuration.xml:34
@@ -86,7 +103,7 @@
msgid ""
"An example of a Server Peer configuration is presented below. Note that not "
"all values for the server peer's attributes are specified in the example"
-msgstr ""
+msgstr "下面是一个 Server Peer 配置的例子。请注意这个例子并没有指定所有 Server Peer 属性的值。"
#. Tag: programlisting
#: Configuration.xml:37
@@ -222,6 +239,135 @@
"\n"
" </mbean>"
msgstr ""
+"<mbean code=\"org.jboss.jms.server.ServerPeer\"\n"
+" name=\"jboss.messaging:service=ServerPeer\"\n"
+" xmbean-dd=\"xmdesc/ServerPeer-xmbean.xml\">\n"
+"\n"
+" <!-- The unique id of the server peer - in a cluster each node MUST "
+"have a unique value - must be an integer -->\n"
+"\n"
+" <attribute name=\"ServerPeerID\">0</attribute>\n"
+" \n"
+" <!-- The default JNDI context to use for queues when they are "
+"deployed without specifying one --> \n"
+" \n"
+" <attribute name=\"DefaultQueueJNDIContext\">/queue</"
+"attribute>\n"
+" \n"
+" <!-- The default JNDI context to use for topics when they are "
+"deployed without specifying one --> \n"
+" \n"
+" <attribute name=\"DefaultTopicJNDIContext\">/topic</"
+"attribute>\n"
+"\n"
+" <attribute name=\"PostOffice\">jboss.messaging:"
+"service=PostOffice</attribute>\n"
+" \n"
+" <!-- The JAAS security domain to use for JBoss Messaging --"
+">\n"
+" \n"
+" <attribute name=\"SecurityDomain\">java:/jaas/messaging</"
+"attribute>\n"
+" \n"
+" <!-- The default security configuration to apply to destinations - "
+"this can be overridden on a per destination basis -->\n"
+" \n"
+" <attribute name=\"DefaultSecurityConfig\">\n"
+" <security>\n"
+" <role name=\"guest\" read=\"true\" write=\"true\" create="
+"\"true\"/>\n"
+" </security>\n"
+" </attribute>\n"
+" \n"
+" <!-- The default Dead Letter Queue (DLQ) to use for destinations.\n"
+" This can be overridden on a per destinatin basis -->\n"
+" \n"
+" <attribute name=\"DefaultDLQ\">jboss.messaging.destination:"
+"service=Queue,name=DLQ</attribute>\n"
+" \n"
+" <!-- The default maximum number of times to attempt delivery of a "
+"message before sending to the DLQ (if configured).\n"
+" This can be overridden on a per destinatin basis -->\n"
+" \n"
+" <attribute name=\"DefaultMaxDeliveryAttempts\">10</"
+"attribute>\n"
+" \n"
+" <!-- The default Expiry Queue to use for destinations. This can be "
+"overridden on a per destinatin basis -->\n"
+" \n"
+" <attribute name=\"DefaultExpiryQueue\">jboss.messaging."
+"destination:service=Queue,name=ExpiryQueue</attribute>\n"
+" \n"
+" <!-- The default redelivery delay to impose. This can be overridden "
+"on a per destination basis -->\n"
+" \n"
+" <attribute name=\"DefaultRedeliveryDelay\">0</attribute>\n"
+" \n"
+" <!-- The periodicity of the message counter manager enquiring on "
+"queues for statistics -->\n"
+" \n"
+" <attribute name=\"MessageCounterSamplePeriod\">5000</"
+"attribute>\n"
+" \n"
+" <!-- The maximum amount of time for a client to wait for failover "
+"to start on the server side after\n"
+" it has detected failure -->\n"
+" \n"
+" <attribute name=\"FailoverStartTimeout\">60000</"
+"attribute>\n"
+" \n"
+" <!-- The maximum amount of time for a client to wait for failover "
+"to complete on the server side after\n"
+" it has detected failure -->\n"
+" \n"
+" <attribute name=\"FailoverCompleteTimeout\">300000</"
+"attribute>\n"
+" \n"
+" <!-- The maximum number of days results to maintain in the message "
+"counter history -->\n"
+" \n"
+" <attribute name=\"DefaultMessageCounterHistoryDayLimit\">-1</"
+"attribute>\n"
+" \n"
+" <!-- The name of the connection factory to use for creating "
+"connections between nodes to pull messages -->\n"
+" \n"
+" <attribute name=\"ClusterPullConnectionFactoryName\">jboss."
+"messaging.connectionfactory:service=ClusterPullConnectionFactory</"
+"attribute>\n"
+" \n"
+" <!-- When redistributing messages in the cluster. Do we need to "
+"preserve the order of messages received\n"
+" by a particular consumer from a particular producer? -->\n"
+" \n"
+" <attribute name=\"DefaultPreserveOrdering\">false</"
+"attribute>\n"
+" \n"
+" <!-- Max. time to hold previously delivered messages back waiting "
+"for clients to reconnect after failover -->\n"
+" \n"
+" <attribute name=\"RecoverDeliveriesTimeout\">300000</"
+"attribute>\n"
+" \n"
+" <attribute name=\"EnableMessageCounters\">false</"
+"attribute> \n"
+"\n"
+" <!-- The password used by the message sucker connections to create "
+"connections.\n"
+" THIS SHOULD ALWAYS BE CHANGED AT INSTALL TIME TO SECURE SYSTEM\n"
+" <attribute name=\"SuckerPassword\"></attribute>\n"
+" -->\n"
+"\n"
+" <depends optional-attribute-name=\"PersistenceManager\">jboss."
+"messaging:service=PersistenceManager</depends>\n"
+" \n"
+" <depends optional-attribute-name=\"JMSUserManager\">jboss."
+"messaging:service=JMSUserManager</depends>\n"
+" \n"
+" <depends>jboss.messaging:service=Connector,"
+"transport=bisocket</depends>\n"
+"\n"
+" </mbean>"
#. Tag: para
#: Configuration.xml:39
@@ -233,24 +379,26 @@
"that knows the default value will be able to access to all destinations on "
"the server. The password chosen should only be exposed to administrators"
msgstr ""
+"安全风险！要避免安全风险，你必须指定 Server Peer 配置文件（messaging-service.xml）里的 SuckerPassword "
+"属性的值。如果你没有进行指定，缺省值将被使用。任何知道缺省值的人都可以访问服务器上的所有目的地。只有管理员才应该知道这个密码。"
#. Tag: title
#: Configuration.xml:49
#, no-c-format
msgid "ServerPeer attributes"
-msgstr ""
+msgstr "ServerPeer 的属性"
#. Tag: para
#: Configuration.xml:50
#, no-c-format
msgid "We will now discuss the MBean attributes of the ServerPeer MBean."
-msgstr ""
+msgstr "现在我们将讨论 ServerPeer MBean 的 MBean 属性。"
#. Tag: title
#: Configuration.xml:53
#, no-c-format
msgid "ServerPeerID"
-msgstr ""
+msgstr "ServerPeerID"
#. Tag: para
#: Configuration.xml:54
@@ -260,47 +408,49 @@
"id. This applies to different nodes that form a cluster as well as nodes "
"that are only linked via a message bridge. The id must be a valid integer."
msgstr ""
+"Server peer 的唯一 ID。你部署的每个节点都必须有唯一的 ID。这适用于组成群集的不同节点，也适用于仅通过消息桥链接的节点。这个 ID "
+"必须为有效的整型值。"
#. Tag: title
#: Configuration.xml:60
#, no-c-format
msgid "DefaultQueueJNDIContext"
-msgstr ""
+msgstr "DefaultQueueJNDIContext"
#. Tag: para
#: Configuration.xml:61
#, no-c-format
msgid ""
"The default JNDI context to use when binding queues. Defaults to /queue."
-msgstr ""
+msgstr "绑定队列时使用的缺省 JNDI 上下文。缺省为 /queue。"
#. Tag: title
#: Configuration.xml:65
#, no-c-format
msgid "DefaultTopicJNDIContext"
-msgstr ""
+msgstr "DefaultTopicJNDIContext"
#. Tag: para
#: Configuration.xml:66
#, no-c-format
msgid ""
"The default JNDI context to use when binding topics. Defaults to /topic."
-msgstr ""
+msgstr "绑定主题时使用的缺省 JNDI 上下文。缺省为 /topic。"
#. Tag: title
#: Configuration.xml:70
#, no-c-format
msgid "PostOffice"
-msgstr ""
+msgstr "PostOffice"
#. Tag: para
#: Configuration.xml:71
-#, no-c-format
+#, fuzzy, no-c-format
msgid ""
"This is the post office that the ServerPeer uses. Normally, you wouldn't "
"have to change this attribute. The post office is responsible for routing "
"messages to queues and maintaining the mapping between addresses and queues."
-msgstr ""
+msgstr "这是 ServerPeer 使用的邮局（Post Office）。"
#. Tag: title
#: Configuration.xml:76
@@ -3768,3 +3918,4 @@
"therefore imperative that the relevant sections are overwritten with the "
"remoting configuration from the JBM distribution."
msgstr ""
+
Modified: projects/docs/enterprise/4.3/Messaging/JBoss_Messaging_User_Guide/zh-CN/Important_Features.po
===================================================================
--- projects/docs/enterprise/4.3/Messaging/JBoss_Messaging_User_Guide/zh-CN/Important_Features.po 2008-07-11 12:09:42 UTC (rev 75681)
+++ projects/docs/enterprise/4.3/Messaging/JBoss_Messaging_User_Guide/zh-CN/Important_Features.po 2008-07-11 12:19:04 UTC (rev 75682)
@@ -1,35 +1,38 @@
# Language zh-CN translations for JBoss_Messaging_User_Guide package.
# Copyright (C) 2008 Free Software Foundation, Inc.
+#
# Automatically generated, 2008.
-#
+# Xi HUANG <xhuang at redhat.com>, 2008.
msgid ""
msgstr ""
"Project-Id-Version: JBoss_Messaging_User_Guide 4.3\n"
"POT-Creation-Date: 2001-02-09 01:25+0100\n"
-"PO-Revision-Date: 2001-02-09 01:25+0100\n"
-"Last-Translator: Automatically generated\n"
-"Language-Team: none\n"
+"PO-Revision-Date: 2008-07-11 14:28+1000\n"
+"Last-Translator: Xi HUANG <xhuang at redhat.com>\n"
+"Language-Team: Chinese Simplified <kde-i18n-doc at lists.kde.org>\n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=UTF-8\n"
"Content-Transfer-Encoding: 8bit\n"
+"X-Generator: KAider 0.1\n"
+"Plural-Forms: nplurals=2; plural=n != 1;\n"
#. Tag: title
#: Important_Features.xml:3
#, no-c-format
msgid "JBoss Messaging - A Quick Tour"
-msgstr ""
+msgstr "JBoss Messaging - 快速教程"
#. Tag: title
#: Important_Features.xml:5
#, no-c-format
msgid "Limitations of JBossMQ"
-msgstr ""
+msgstr "JBossMQ 的局限性"
#. Tag: para
#: Important_Features.xml:6
#, no-c-format
msgid "JBossMQ has two fundamental limitations:"
-msgstr ""
+msgstr "JBossMQ 有两个根本的局限性："
#. Tag: para
#: Important_Features.xml:10
@@ -37,7 +40,7 @@
msgid ""
"JBossMQ is based on SpyderMQ (the open source project) which is a non-"
"clustered broker."
-msgstr ""
+msgstr "JBossMQ 基于非群集的 SpyderMQ（一个开源项目）。"
#. Tag: para
#: Important_Features.xml:15
@@ -45,13 +48,13 @@
msgid ""
"The threading model and the overall design of the non-clustered broker leads "
"to performance limitations in certain high load usage scenarios."
-msgstr ""
+msgstr "它的线程模型和非群集设计在某些高负载情形下会导致性能问题。"
#. Tag: title
#: Important_Features.xml:23
#, no-c-format
msgid "JBoss Messaging Features"
-msgstr ""
+msgstr "JBoss Messaging 的特征"
#. Tag: para
#: Important_Features.xml:24
@@ -62,6 +65,9 @@
"Oriented Architectures(SOAs), Enterprise Service Buses (ESBs) and other "
"integration needs ranging from the simplest to the highest demand networks."
msgstr ""
+"JBoss Messaging 实现了一个高性能和稳定的消息核心，它的设计目的是为了最大限度地利用面向服务架构（Service Oriented "
+"Architectures，SOA）、企业级服务总线（Enterprise Service "
+"Buses，ESB）以及其他从最简单到最高要求的网络的集成需要。"
#. Tag: para
#: Important_Features.xml:27
@@ -76,6 +82,8 @@
"in a standards-based format as well as being designed to be able to support "
"other messaging protocols in the future."
msgstr ""
+"它将允许你在群集系统里顺利地分布应用程序负载，智能地平衡和利用每个节点的 CPU 周期。它没有单个故障点和瓶颈，但它具有复杂和完全可配置的消息过期管理和 "
+"XA 事务恢复，因此提供了具有高可扩充性和性能的群集实现。它也包括了以基于标准的格式递送消息且能够支持将来的其他消息协议的 JMS 前端。"
#. Tag: para
#: Important_Features.xml:31
@@ -85,24 +93,26 @@
"JMS 1.1 implementation, that currently works with JBoss Enterprise "
"Application Platform 4.3 or JBoss Application Server version 4.2 or later."
msgstr ""
+"<emphasis>JMS compliance</emphasis>：完全兼容和经 Sun 认证的 JMS 1.1 实现，可以在 JBoss "
+"企业级应用程序平台 4.2、4.3 或更新版本里使用。"
#. Tag: para
#: Important_Features.xml:35
#, no-c-format
msgid "JBoss Messaging contains a host of other features, including:"
-msgstr ""
+msgstr "JBoss Messaging 还包含了其他功能："
#. Tag: para
#: Important_Features.xml:39
#, no-c-format
msgid "Publish-subscribe and point-to-point messaging models"
-msgstr ""
+msgstr "发布-订阅和点到点消息模型"
#. Tag: para
#: Important_Features.xml:42
#, no-c-format
msgid "Persistent and non-persistent messages"
-msgstr ""
+msgstr "持久的和非持久的消息"
#. Tag: para
#: Important_Features.xml:45
@@ -110,19 +120,19 @@
msgid ""
"Guaranteed message delivery that ensures that messages arrive once and only "
"once where required"
-msgstr ""
+msgstr "确保消息在有需要时只到达一次的消息递送保证"
#. Tag: para
#: Important_Features.xml:49
#, no-c-format
msgid "Transactional and reliable - supporting ACID semantics"
-msgstr ""
+msgstr "事务性和可靠性 － 支持 ACID 模式"
#. Tag: para
#: Important_Features.xml:53
#, no-c-format
msgid "Customizable security framework based on JAAS"
-msgstr ""
+msgstr "基于 JAAS 的可定制的安全框架"
#. Tag: para
#: Important_Features.xml:56
@@ -130,13 +140,13 @@
msgid ""
"Fully integrated with JBoss Transactions (formerly known as Arjuna JTA) for "
"full transaction recoverability."
-msgstr ""
+msgstr "和 JBoss Transactions（以前称为 Arjuna JTA）完全集成，具有完全事务恢复能力。"
#. Tag: para
#: Important_Features.xml:60
#, no-c-format
msgid "Extensive JMX management interface"
-msgstr ""
+msgstr "扩展的 JMX 管理接口"
#. Tag: para
#: Important_Features.xml:63
@@ -144,26 +154,26 @@
msgid ""
"Support for most major databases including Oracle, Sybase, MS SQL Server, "
"PostgreSQL and MySQL"
-msgstr ""
+msgstr "对 Oracle、Sybase、MS SQL Server、PostgreSQL 和 MySQL 等主要数据库的支持"
#. Tag: para
#: Important_Features.xml:67
#, no-c-format
msgid ""
"HTTP transport to allow use through firewalls that only allow HTTP traffic"
-msgstr ""
+msgstr "通过 HTTP 传输使用只允许 HTTP 通信的防火墙"
#. Tag: para
#: Important_Features.xml:71
#, no-c-format
msgid "SSL transport"
-msgstr ""
+msgstr "SSL 传输"
#. Tag: para
#: Important_Features.xml:74
#, no-c-format
msgid "Configurable DLQs (Dead Letter Queues) and Expiry Queues"
-msgstr ""
+msgstr "可配置的 DLQs (Dead Letter Queues) 和 Expiry Queue"
#. Tag: para
#: Important_Features.xml:78
@@ -171,7 +181,7 @@
msgid ""
"Message statistics: Gives you a rolling historical view of what messages "
"were delivered to what queues and subscriptions"
-msgstr ""
+msgstr "消息统计：给你关于递送给不同队列和订阅的不同消息的历史数据视图"
#. Tag: para
#: Important_Features.xml:83
@@ -179,19 +189,19 @@
msgid ""
"Automatic paging of messages to storage. Allows the use of very large queues "
"- too large to fit in memory at once"
-msgstr ""
+msgstr "消息到存储的自动分页。这允许你使用非常大的队列 － 大到不能马上存放在内存里"
#. Tag: title
#: Important_Features.xml:90
#, no-c-format
msgid "Clustering Features"
-msgstr ""
+msgstr "群集功能"
#. Tag: title
#: Important_Features.xml:92
#, no-c-format
msgid "Fully clustered queues and topics"
-msgstr ""
+msgstr "群集队列和主题"
#. Tag: para
#: Important_Features.xml:93
@@ -296,7 +306,7 @@
#: Important_Features.xml:134
#, no-c-format
msgid "Message bridge"
-msgstr ""
+msgstr "消息桥（Message Bridge）"
#. Tag: para
#: Important_Features.xml:135
@@ -350,3 +360,4 @@
"JBoss Messaging is built against the JBoss AS 4.2 libraries which are built "
"using Java 5. Therefore JBoss Messaging only runs with Java 5 or later."
msgstr ""
+
More information about the jboss-cvs-commits
mailing list