[jboss-cvs] JBossAS SVN: r75747 - 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
Mon Jul 14 00:45:46 EDT 2008
Author: xhuang at jboss.com
Date: 2008-07-14 00:45:46 -0400 (Mon, 14 Jul 2008)
New Revision: 75747
Modified:
projects/docs/enterprise/4.3/Messaging/JBoss_Messaging_User_Guide/zh-CN/Bridge.po
projects/docs/enterprise/4.3/Messaging/JBoss_Messaging_User_Guide/zh-CN/C_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/Bridge.po
===================================================================
--- projects/docs/enterprise/4.3/Messaging/JBoss_Messaging_User_Guide/zh-CN/Bridge.po 2008-07-14 04:29:52 UTC (rev 75746)
+++ projects/docs/enterprise/4.3/Messaging/JBoss_Messaging_User_Guide/zh-CN/Bridge.po 2008-07-14 04:45:46 UTC (rev 75747)
@@ -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-14 11:32+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
#: Bridge.xml:3
#, no-c-format
msgid "JBoss Messaging Message Bridge Configuration"
-msgstr ""
+msgstr "JBoss Messaging 消息桥的配置"
#. Tag: title
#: Bridge.xml:5
#, no-c-format
msgid "Message bridge overview"
-msgstr ""
+msgstr "消息桥概述"
#. Tag: para
#: Bridge.xml:6
#, no-c-format
msgid "JBoss Messaging includes a fully functional message bridge."
-msgstr ""
+msgstr "JBoss Messaging 包含一个功能完整的消息桥。"
#. Tag: para
#: Bridge.xml:7
@@ -38,7 +41,7 @@
"The function of the bridge is to consume messages from a source queue or "
"topic, and send them to a target queue or topic, typically on a different "
"server."
-msgstr ""
+msgstr "消息桥的功能是从源队列或主题里提取消息，然后发送到通常在另外一个服务器上的目标队列或主题。"
#. Tag: para
#: Bridge.xml:10
@@ -48,7 +51,7 @@
"makes bridging suitable for reliably sending messages from one cluster to "
"another, for instance across a WAN, and where the connection may be "
"unreliable."
-msgstr ""
+msgstr "源和目标服务器不需要位于同一个群集里，消息桥适合于把消息可靠地从一个群集发送到另外一个群集，例如跨越网络连接可能不稳定的广域网。"
#. Tag: para
#: Bridge.xml:14
@@ -57,7 +60,7 @@
"A bridge is deployed inside a JBoss AS instance. The instance can be the "
"same instance as either the source or target server. Or could be on a third, "
"separate JBoss AS instance."
-msgstr ""
+msgstr "消息桥部署在 JBoss AS 实例里。这个实例可以是源或目标服务器里的实例，也可以是第三个独立的 JBoss AS 实例。"
#. Tag: para
#: Bridge.xml:17
@@ -67,6 +70,8 @@
"just drop the MBean descriptor into the deploy directory of a JBoss "
"configuration which contains JBoss Messaging."
msgstr ""
+"消息桥作为 MBean 部署在 JBoss AS 实例里。部署很简单 － 只要把 MBean 部署描述符放入包含 JBoss Messaging 的 "
+"JBoss 配置的 deploy 目录下就可以了。"
#. Tag: para
#: Bridge.xml:20
@@ -76,6 +81,7 @@
"deployed in JBoss AS, and moving messages from the source to the target "
"destination"
msgstr ""
+"docs/example/bridge 里的例子演示了部署在 JBoss AS 里的一个简单的消息桥，它把消息从源服务器一移动到目标目的地里。"
#. Tag: para
#: Bridge.xml:23
@@ -83,7 +89,7 @@
msgid ""
"The bridge can also be used to bridge messages from other non JBoss "
"Messaging JMS servers, as long as they are JMS 1.1 compliant."
-msgstr ""
+msgstr "消息桥也可以用转移非 JBoss Messaging JMS 服务器的消息，只要这个服务器兼容 JMS 1.1。"
#. Tag: para
#: Bridge.xml:26
@@ -94,6 +100,7 @@
"connecting to the source and/or target until they come back online. When it "
"comes back online it will resume operation as normal."
msgstr ""
+"消息桥具有处理故障的能力，如果源或目标服务器连接丢失了（例如网络故障），消息桥将试图恢复连接，直到双方都在线为止。当连接恢复后，消息桥将继续正常的操作。"
#. Tag: para
#: Bridge.xml:31
@@ -101,7 +108,7 @@
msgid ""
"The bridge can be configured with an optional JMS selector, so it will only "
"consume messages matching that JMS selector"
-msgstr ""
+msgstr "消息桥可以用可选的 JMS Selector 进行配置，所以它只提取符合该 JMS selector 的消息。"
#. Tag: para
#: Bridge.xml:33
@@ -110,7 +117,7 @@
"It can be configured to consume from a queue or a topic. When it consumes "
"from a topic it can be configured to consume using a non durable or durable "
"subscription"
-msgstr ""
+msgstr "它可以配置成从队列或主题里提取消息。当它从主题里提取消息时，你还可以配置它使用非持久的或持久的订阅。"
#. Tag: para
#: Bridge.xml:36
@@ -118,13 +125,13 @@
msgid ""
"The bridge can be configured to bridge messages with one of three levels of "
"quality of service, they are:"
-msgstr ""
+msgstr "消息桥可以使用三个级别的服务品质来转发消息，它们是："
#. Tag: para
#: Bridge.xml:40
#, no-c-format
msgid "QOS_AT_MOST_ONCE"
-msgstr ""
+msgstr "QOS_AT_MOST_ONCE"
#. Tag: para
#: Bridge.xml:41
@@ -137,6 +144,9 @@
"destination they could be lost. Hence delivery will occur at most once. This "
"mode is avilable for both persistent and non persistent messages."
msgstr ""
+"使用这种 QoS "
+"模式，消息最多可以从源服务器到达目的地一次。在发送到目的地之前，消息从源服务器里提取并确认。因此，如果在从源服务器提取和到达目的地之间如果发生故障，消息就"
+"有可能会丢失。因此，递送最多只能进行一次。这种模式对持久性和非持久性消息都适用。"
#. Tag: para
#: Bridge.xml:51
@@ -689,3 +699,4 @@
"once each message-id will be appended. This enables a distributed request-"
"response pattern to be used"
msgstr ""
+
Modified: projects/docs/enterprise/4.3/Messaging/JBoss_Messaging_User_Guide/zh-CN/C_Configuration.po
===================================================================
--- projects/docs/enterprise/4.3/Messaging/JBoss_Messaging_User_Guide/zh-CN/C_Configuration.po 2008-07-14 04:29:52 UTC (rev 75746)
+++ projects/docs/enterprise/4.3/Messaging/JBoss_Messaging_User_Guide/zh-CN/C_Configuration.po 2008-07-14 04:45:46 UTC (rev 75747)
@@ -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-14 14:45+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
#: C_Configuration.xml:3
#, no-c-format
msgid "JBoss Messaging Clustering Configuration"
-msgstr ""
+msgstr "JBoss Messaging 群集配置"
#. Tag: para
#: C_Configuration.xml:4
@@ -27,6 +30,7 @@
"configuration changes. It is however crucial that every node is assigned a "
"unique server id."
msgstr ""
+"在大部分情况下，JBoss Messaging 群集应该可以直接运行而不需要修改任何配置。然而为每个节点都分配一个唯一的服务器 ID 是很重要的。"
#. Tag: para
#: C_Configuration.xml:8
@@ -38,6 +42,8 @@
"clustering you must replace this with a different shared database. If the "
"database is not replaced then clustering will not work."
msgstr ""
+"对于基于群集的安装来说，群集里的每个节点都有一个共享的数据库是强制的。JBoss AS 缺省使用的 HSQLDB "
+"是一个本地的共享数据库。因此，如果要使用群集，你必须用另外的数据库来替换它。"
#. Tag: para
#: C_Configuration.xml:16
@@ -47,19 +53,20 @@
"same IP address, e.g. for development purposes, then you can use the "
"ServiceBindingManager to do this as follows:"
msgstr ""
+"如果你想在同一台机器上运行多个 JBoss Messaging 实例，如出于开发目的，你可以用 ServiceBindingManager 来实现："
#. Tag: para
#: C_Configuration.xml:22
#, no-c-format
msgid ""
"Uncomment binding manager service from $JBOSS_CONFIG/conf/jboss-service.xml"
-msgstr ""
+msgstr "在 $JBOSS_CONFIG/conf/jboss-service.xml 里注释 binding manager 服务"
#. Tag: para
#: C_Configuration.xml:26
#, no-c-format
msgid "Specify the desired port rage (e.g. ports-01, ports-02... etc)"
-msgstr ""
+msgstr "指定端口范围（如ports-01、ports-02 等）"
#. Tag: para
#: C_Configuration.xml:30
@@ -68,6 +75,8 @@
"Look at $JBOSS_HOME/docs/examples/binding-manager/sample-bindings.xml. On "
"each port range, JBoss Remoting configuration should look like:"
msgstr ""
+"来看看 $JBOSS_HOME/docs/examples/binding-manager/sample-bindings.xml。针对每个端口范围的 "
+"JBoss Remoting 配置都应该类似于："
#. Tag: programlisting
#: C_Configuration.xml:34
@@ -124,6 +133,56 @@
" <binding port=\"4657\"/>\n"
" </service-config>"
msgstr ""
+"<service-config name=\"jboss.messaging:service=Connector,"
+"transport=bisocket\"\n"
+" delegateClass=\"org.jboss.services.binding."
+"AttributeMappingDelegate\">\n"
+" <delegate-config>\n"
+" <attribute name=\"Configuration\"><![CDATA[\n"
+" <config>\n"
+" <invoker transport=\"bisocket\">\n"
+" <attribute name=\"marshaller\" isParam=\"true\">\n"
+" org.jboss.jms.wireformat.JMSWireFormat\n"
+" </attribute>\n"
+" <attribute name=\"unmarshaller\" isParam=\"true\">\n"
+" org.jboss.jms.wireformat.JMSWireFormat\n"
+" </attribute>\n"
+" <attribute name=\"dataType\" isParam=\"true\">jms</"
+"attribute>\n"
+" <attribute name=\"socket.check_connection\" isParam=\"true"
+"\">false</attribute>\n"
+" <attribute name=\"timeout\" isParam=\"true\">0</"
+"attribute>\n"
+" <attribute name=\"serverBindAddress\">${jboss.bind."
+"address}</attribute>\n"
+" <attribute name=\"serverBindPort\">4657</"
+"attribute>\n"
+" <attribute name=\"leasePeriod\">10000</"
+"attribute>\n"
+" <attribute name=\"clientSocketClass\" isParam=\"true"
+"\">\n"
+" org.jboss.jms.client.remoting.ClientSocketWrapper\n"
+" </attribute>\n"
+" <attribute name=\"serverSocketClass\">\n"
+" org.jboss.jms.server.remoting.ServerSocketWrapper\n"
+" </attribute>\n"
+" <attribute name=\"numberOfRetries\" isParam=\"true"
+"\">1</attribute>\n"
+" <attribute name=\"numberOfCallRetries\" isParam=\"true"
+"\">1</attribute>\n"
+" <attribute name=\"clientMaxPoolSize\" isParam=\"true"
+"\">50</attribute>\n"
+" </invoker>\n"
+" <handlers>\n"
+" <handler subsystem=\"JMS\">\n"
+" org.jboss.jms.server.remoting.JMSServerInvocationHandler\n"
+" </handler>\n"
+" </handlers>\n"
+" </config>\n"
+" ]]></attribute>\n"
+" </delegate-config>\n"
+" <binding port=\"4657\"/>\n"
+" </service-config>"
#. Tag: para
#: C_Configuration.xml:35
@@ -137,6 +196,10 @@
"is out of date and you will need to copy the config from <literal>remoting-"
"bisocket-service.xml</literal>"
msgstr ""
+"你必须确保这个配置（如上所示）和 <literal>remoting-bisocket-service.xml</literal> "
+"里的一样，除了每个端口范围的实际 serverBindPort 必须不同。请注意，JBAS 4.2.0 附带的<literal>"
+"sample-bindings.xml</literal> 里的缺省 JBoss Messaging 服务 binding manager "
+"绑定是过期的，你需要从 <literal>remoting-bisocket-service.xml</literal> 里把相关配置复制过来。"
#. Tag: para
#: C_Configuration.xml:45
@@ -144,13 +207,13 @@
msgid ""
"You should ensure that each node is configured to use a different ports "
"range."
-msgstr ""
+msgstr "你应该确保每个节点使用不同的端口范围。"
#. Tag: title
#: C_Configuration.xml:50
#, no-c-format
msgid "Unique server peer id"
-msgstr ""
+msgstr "唯一的 server peer id"
#. Tag: para
#: C_Configuration.xml:51
@@ -158,7 +221,7 @@
msgid ""
"Every node deployed must have a unique id, including those in a particular "
"LAN cluster, and also those only linked by mesage bridges."
-msgstr ""
+msgstr "每个部署的节点必须具有唯一的 ID，这包括特殊局域网群集里的节点，以及只通过消息桥链接的节点。"
#. Tag: para
#: C_Configuration.xml:54
@@ -168,12 +231,14 @@
"<filename>messaging-service.xml</filename> is unique for each node on the "
"cluster. The <literal>ServerPeerID</literal> value must be a valid integer."
msgstr ""
+"确保 <filename>messaging-service.xml</filename> 里针对群集里的每个节点的 <literal>"
+"ServerPeerID</literal> MBean 属性值是唯一的。<literal>ServerPeerID</literal> 必须为整型值。"
#. Tag: title
#: C_Configuration.xml:61
#, no-c-format
msgid "Clustered destinations"
-msgstr ""
+msgstr "群集目的地"
#. Tag: para
#: C_Configuration.xml:62
@@ -185,6 +250,9 @@
"clustered simply set the clustered attribute in the destination deployment "
"descriptor to true."
msgstr ""
+"JBoss Messaging 透明地群集了 JMS "
+"队列和主题。发送到分布式队列或主题的消息也可在其他节点上获取。要指定特定节点为群集的，只要设置目的地部署描述符里的 clustered 属性为 true "
+"就可以了。"
#. Tag: para
#: C_Configuration.xml:67
@@ -192,7 +260,7 @@
msgid ""
"JBoss Messaging balances messages between nodes, catering for faster or "
"slower consumers to efficiently balance processing load across the cluster."
-msgstr ""
+msgstr "JBoss Messaging 在节点间平衡消息的负载，这是为了有效地调整群集里较快和较慢消费者的负载。"
#. Tag: para
#: C_Configuration.xml:70
@@ -203,12 +271,14 @@
"this by not specifying the attribute ClusterPullConnectionFactoryName on the "
"server peer"
msgstr ""
+"如果你不想在节点间重新分发消息，但仍然想保留群集目的地的其他特点，你可以通过不指定 server peer 上的 "
+"ClusterPullConnectionFactoryName 属性来实现这一点。"
#. Tag: title
#: C_Configuration.xml:76
#, no-c-format
msgid "Clustered durable subs"
-msgstr ""
+msgstr "群集的持久性订阅"
#. Tag: para
#: C_Configuration.xml:77
@@ -219,12 +289,14 @@
"different nodes of the cluster. A durable subscription will be clustered if "
"it's topic is clustered"
msgstr ""
+"JBoss Messaging 的持久性订阅（durable "
+"subscription）也可以进行群集。这意味着多个订阅者可以在不同节点里访问相同的持久性订阅。如果持久性订阅的主题是群集的，那么它也将是群集的。"
#. Tag: title
#: C_Configuration.xml:84
#, no-c-format
msgid "Clustered temporary destinations"
-msgstr ""
+msgstr "群集的临时目的地"
#. Tag: para
#: C_Configuration.xml:85
@@ -232,13 +304,13 @@
msgid ""
"JBoss Messaging also supports clustered temporary topics and queues. All "
"temporary topics and queues will be clustered if the post office is clustered"
-msgstr ""
+msgstr "JBoss Messaging 也支持群集的临时主题和队列。如果邮局（Post Office）是群集的，那么所有的临时主题和队列将被群集。"
#. Tag: title
#: C_Configuration.xml:91
#, no-c-format
msgid "Non clustered servers"
-msgstr ""
+msgstr "非群集的服务器"
#. Tag: para
#: C_Configuration.xml:92
@@ -247,13 +319,13 @@
"If you don't want your nodes to participate in a cluster, or only have one "
"non clustered server you can set the clustered attribute on the postoffice "
"to false"
-msgstr ""
+msgstr "如果你不希望你的节点参与某个群集，或者你只有一个非群集的服务器，你可以设置邮局的 clustered 属性为 false。"
#. Tag: title
#: C_Configuration.xml:99
#, no-c-format
msgid "Message ordering in the cluster"
-msgstr ""
+msgstr "管理群集里的顺序"
#. Tag: para
#: C_Configuration.xml:100
@@ -266,12 +338,15 @@
"this to true is that messages cannot be distributed as freely around the "
"cluster"
msgstr ""
+"如果你想对消息应用严格的 JMS 顺序，亦即特定的 JMS "
+"消费者（consumer）将按照和生产者（producer）产生消息的顺序来消费消息，你可以设置 server peer 里的 "
+"DefaultPreserveOrdering 属性为 true。它的缺省值是 false。设置它为 true 的副作用是消息不能自由地在群集里进行分发。"
#. Tag: title
#: C_Configuration.xml:110
#, no-c-format
msgid "Idempotent operations"
-msgstr ""
+msgstr "Idempotent 操作"
#. Tag: para
#: C_Configuration.xml:111
@@ -292,6 +367,11 @@
"them if they arrive. Duplicate checking is a very powerful technique that "
"can remove the need for XA transactions in many cases."
msgstr ""
+"如果对发送持久性消息到持久性目的地的调用成功返回，那么你可以确认消息已经被持久化了。然而，如果这个调用没有成功返回，例如有异常被抛出，你并不能确认消息没有"
+"被持久化。因为故障可能发生在消息已经被持久化后，而在响应调用者之前。这是任何 RPC "
+"类型的调用的一个共同问题：调用没有返回并不代表它没有成功执行。不管它是一个 web 服务调用、HTTP 的 GET 请求，还是 EJB "
+"调用，都是如此。编程的诀窍是使这些操作成为幂等的（idempotent），也就是它们可以重复而不会使系统的状态不一致。对于消息系统来说，你可以在应用程序级"
+"别上来实现这一点，也就是检查重复的消息并在其到达时丢弃它们。对重复的检查是一种非常强大的技术，在许多情况下它可以消除对 XA 事务的需要。"
#. Tag: para
#: C_Configuration.xml:126
@@ -299,13 +379,13 @@
msgid ""
"In the clustered case, JBM is by default configured to automatically detect "
"duplicate messages."
-msgstr ""
+msgstr "而在群集环境里，JBM 将缺省自动检测重复的消息。"
#. Tag: title
#: C_Configuration.xml:131
#, no-c-format
msgid "Clustered connection factories"
-msgstr ""
+msgstr "群集的连接工厂"
#. Tag: para
#: C_Configuration.xml:132
@@ -315,6 +395,7 @@
"true then consecutive create connection attempts will round robin between "
"available servers. The first node to try is chosen randomly"
msgstr ""
+"如果连接工厂的 supportsLoadBalancing 属性为 true，那么它将在可用的服务器间循环地尝试创建连接。第一个尝试的节点将被随机地选择。"
#. Tag: para
#: C_Configuration.xml:133
@@ -324,6 +405,8 @@
"then automatic failover is enabled. This will automatically failover from "
"one server to another, transparently to the user, in case of failure."
msgstr ""
+"如果连接工厂的 supportsFailover 属性为 "
+"true，那么自动失效切换将被启用。在故障发生是，这将自动地从一个服务器切换到另外一个服务器，而对于用户来说是透明的。"
#. Tag: para
#: C_Configuration.xml:135
@@ -335,3 +418,6 @@
"connection failure. You would then need to manually close the connection, "
"lookup a new connection factory from HA JNDI and recreate the connection."
msgstr ""
+"如果不要求自动失效切换或者你想手工来完成（JBoss MQ 风格），你可以将其设置为 false，而且你可以为连接提供一个标准的 JMS "
+"ExceptionListener，它在连接发生故障时将被调用。然后你需要手工关闭这个连接，从 HA JNDI 里查找一个新的连接工厂并重新创建连接。"
+
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-14 04:29:52 UTC (rev 75746)
+++ projects/docs/enterprise/4.3/Messaging/JBoss_Messaging_User_Guide/zh-CN/Important_Features.po 2008-07-14 04:45:46 UTC (rev 75747)
@@ -7,7 +7,7 @@
msgstr ""
"Project-Id-Version: JBoss_Messaging_User_Guide 4.3\n"
"POT-Creation-Date: 2001-02-09 01:25+0100\n"
-"PO-Revision-Date: 2008-07-13 22:03+1000\n"
+"PO-Revision-Date: 2008-07-14 11:57+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"
@@ -201,7 +201,7 @@
#: Important_Features.xml:92
#, no-c-format
msgid "Fully clustered queues and topics"
-msgstr "群集队列和主题"
+msgstr "完全群集的队列和主题"
#. Tag: para
#: Important_Features.xml:93
@@ -209,13 +209,13 @@
msgid ""
"\"Logical\" queues and topics are distributed across the cluster. You can "
"send to a queue or a topic from any node, and receive from any other."
-msgstr ""
+msgstr "“逻辑的”队列和主题分布在整个群集里。你可以向任何节点的队列和主题发送消息和接受消息。"
#. Tag: title
#: Important_Features.xml:98
#, no-c-format
msgid "Fully clustered durable subscriptions"
-msgstr ""
+msgstr "群集的持久性订阅"
#. Tag: para
#: Important_Features.xml:99
@@ -224,13 +224,13 @@
"A particular durable subscription can be accessed from any node of the "
"cluster - allowing you to spread processing load from that subscription "
"across the cluster."
-msgstr ""
+msgstr "你可以从群集里任何节点访问特定的持久性订阅 － 这允许把订阅的负载分摊到整个群集里。"
#. Tag: title
#: Important_Features.xml:104
#, no-c-format
msgid "Fully clustered temporary queues"
-msgstr ""
+msgstr "完全群集的临时队列"
#. Tag: para
#: Important_Features.xml:105
@@ -238,13 +238,13 @@
msgid ""
"Send a message with a <literal>replyTo</literal> of a temp queue and it can "
"be sent back on any node of the cluster."
-msgstr ""
+msgstr "如果发送带有 <literal>replyTo</literal> 临时队列的消息，它就可以送回群集里的任何节点。"
#. Tag: title
#: Important_Features.xml:110
#, no-c-format
msgid "Intelligent message redistribution"
-msgstr ""
+msgstr "智能消息重分布"
#. Tag: para
#: Important_Features.xml:111
@@ -253,13 +253,13 @@
"Messages are automatically moved between different nodes of the cluster if "
"consumers are faster on one node than another. This can help prevent "
"starvation or build up of messages on particular nodes."
-msgstr ""
+msgstr "如果在某个节点上消费者比另外一个节点块，消息将在群集中的不同节点间自动转移。这有助于防止 starvation 或者在某个节点上堆积消息。"
#. Tag: title
#: Important_Features.xml:116
#, no-c-format
msgid "Message order protection"
-msgstr ""
+msgstr "消息顺序保护"
#. Tag: para
#: Important_Features.xml:117
@@ -269,12 +269,14 @@
"the same as is consumed by a consumer then you can set this to true. This "
"works even in the presence of message redistribution."
msgstr ""
+"如果你想确保生产者（Producer）产生消息的顺序和消费者（Consumer）消费消息的顺序一致，那就把这设置为 "
+"true。这甚至在消息重分布时也可以实现。"
#. Tag: title
#: Important_Features.xml:122
#, no-c-format
msgid "Fully transparent failover"
-msgstr ""
+msgstr "完全透明的失效切换"
#. Tag: para
#: Important_Features.xml:123
@@ -285,6 +287,8 @@
"fall back to exceptions being thrown and manually recreation of connections "
"on another node)"
msgstr ""
+"当某个服务器发生故障时，你的会话将在新的节点上继续进行，就好像什么都没有发生一样。（这是完全可配置的 － "
+"如果你不希望这样，你可以设置为抛出异常并手工在另外节点上重新创建连接）"
#. Tag: title
#: Important_Features.xml:128
More information about the jboss-cvs-commits
mailing list