[jboss-cvs] JBossAS SVN: r75822 - 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
Tue Jul 15 01:36:16 EDT 2008
Author: xhuang at jboss.com
Date: 2008-07-15 01:36:16 -0400 (Tue, 15 Jul 2008)
New Revision: 75822
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/Configuration.po
Log:
udpate
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-15 04:51:09 UTC (rev 75821)
+++ projects/docs/enterprise/4.3/Messaging/JBoss_Messaging_User_Guide/zh-CN/Bridge.po 2008-07-15 05:36:16 UTC (rev 75822)
@@ -1,3 +1,4 @@
+# translation of Bridge.po to
# Language zh-CN translations for JBoss_Messaging_User_Guide package.
# Copyright (C) 2008 Free Software Foundation, Inc.
#
@@ -5,15 +6,15 @@
# Xi HUANG <xhuang at redhat.com>, 2008.
msgid ""
msgstr ""
-"Project-Id-Version: JBoss_Messaging_User_Guide 4.3\n"
+"Project-Id-Version: Bridge\n"
"POT-Creation-Date: 2001-02-09 01:25+0100\n"
-"PO-Revision-Date: 2008-07-14 11:32+1000\n"
+"PO-Revision-Date: 2008-07-15 11:36+1000\n"
"Last-Translator: Xi HUANG <xhuang at redhat.com>\n"
-"Language-Team: Chinese Simplified <kde-i18n-doc at lists.kde.org>\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: KAider 0.1\n"
+"X-Generator: KBabel 1.11.4\n"
"Plural-Forms: nplurals=2; plural=n != 1;\n"
#. Tag: title
@@ -80,8 +81,7 @@
"An example in docs/example/bridge demonstrates a simple bridge being "
"deployed in JBoss AS, and moving messages from the source to the target "
"destination"
-msgstr ""
-"docs/example/bridge 里的例子演示了部署在 JBoss AS 里的一个简单的消息桥，它把消息从源服务器一移动到目标目的地里。"
+msgstr "docs/example/bridge 里的例子演示了部署在 JBoss AS 里的一个简单的消息桥，它把消息从源服务器一移动到目标目的地里。"
#. Tag: para
#: Bridge.xml:23
@@ -99,8 +99,7 @@
"server connetion is lost, e.g. due to network failure, the bridge will retry "
"connecting to the source and/or target until they come back online. When it "
"comes back online it will resume operation as normal."
-msgstr ""
-"消息桥具有处理故障的能力，如果源或目标服务器连接丢失了（例如网络故障），消息桥将试图恢复连接，直到双方都在线为止。当连接恢复后，消息桥将继续正常的操作。"
+msgstr "消息桥具有处理故障的能力，如果源或目标服务器连接丢失了（例如网络故障），消息桥将试图恢复连接，直到双方都在线为止。当连接恢复后，消息桥将继续正常的操作。"
#. Tag: para
#: Bridge.xml:31
@@ -152,7 +151,7 @@
#: Bridge.xml:51
#, no-c-format
msgid "QOS_DUPLICATES_OK"
-msgstr ""
+msgstr "QOS_DUPLICATES_OK"
#. Tag: para
#: Bridge.xml:52
@@ -165,13 +164,13 @@
"system recovers. I.e. the destination might receive duplicates after a "
"failure. This mode is available for both persistent and non persistent "
"messages."
-msgstr ""
+msgstr "使用这种 QoS 模式，消息从源服务器提取并在成功送达目的地后确认收到。因此，如果故障发生在消息发送到目的地之后、而在确认收到之前，系统恢复后消息可能会被再发送一次。也就是说，在发生故障时，目的地可能收到重复的消息。持久性和非持久性消息都可以使用这种模式。"
#. Tag: para
#: Bridge.xml:62
#, no-c-format
msgid "QOS_ONCE_AND_ONLY_ONCE"
-msgstr ""
+msgstr "QOS_ONCE_AND_ONLY_ONCE"
#. Tag: para
#: Bridge.xml:63
@@ -192,6 +191,8 @@
"transaction manager and resource side for recovery. If you require this "
"level of QoS, please be sure to enable XA recovery with JBoss Transactions."
msgstr ""
+"这种 QoS 模式确保消息将只到达目的地一次（有时候这种模式被称为\"exactly once\"）。如果源和目的地都在同一个 JBoss Messaging 服务器实例上，那么这可以通过在同一个本地事务内发送和确认消息来实现。如果源和目的地在不同的服务器上，这可以通过在 JTA 事务里支持发送和消费会话来实现。JTA 事务由 JBoss "
+"Transactions JTA 实现所控制，它是一个可完全恢复的事务管理者（Transaction Manager），因此提供了级别非常高的持久性。如果 JTA 时必需的，那么这两个连接工厂都需要是 XAConnectionFactory 的实现。这种模式仅适用于持久性消息。它可能是最慢的模式，因为它要求登录事务管理者和用于恢复的资源。如果你需要这种级别的 QoS，请确保启用 JBoss Transactions 的 XA 恢复功能。"
#. Tag: para
#: Bridge.xml:80
@@ -206,13 +207,13 @@
"certain period of time so this approach is not as watertight as using "
"QOS_ONCE_AND_ONLY_ONCE but may be a good choice depending on your specific "
"application."
-msgstr ""
+msgstr "对于特殊的应用程序，我们可能提供 once and only once 模式而无需使用 QOS_ONCE_AND_ONLY_ONCE QoS 级别。这可以通过使用 QOS_DUPLICATES_OK 模式并在目的地检查重复消息来实现。我们也可以在应用程序级别来实现：在磁盘上保留一个接收到的消息的 ID 的缓存并比较收到的消息。因为这个缓存将只在某段时间内有效，所以这个方法并不象 QOS_ONCE_AND_ONLY_ONCE 模式一样无懈可击，但也不失为一个好的选择，这取决于特殊应用程序的需要。"
#. Tag: title
#: Bridge.xml:87
#, no-c-format
msgid "Bridge deployment"
-msgstr ""
+msgstr "部署消息桥"
#. Tag: para
#: Bridge.xml:88
@@ -220,19 +221,19 @@
msgid ""
"A message bridge is easily deployed by dropping the MBean descriptor in the "
"deploy directory of your JBoss AS installation which contains JBoss Messaging"
-msgstr ""
+msgstr "只要把相关的 MBean 描述符放入包含 JBoss Messaging 的 JBoss AS 的 deploy 目录下，你就可以轻易地部署消息桥了。"
#. Tag: title
#: Bridge.xml:93
#, no-c-format
msgid "Bridge configuration"
-msgstr ""
+msgstr "消息桥的配置"
#. Tag: para
#: Bridge.xml:94
#, no-c-format
msgid "In this section we describe how to configure the message bridge"
-msgstr ""
+msgstr "本节我们将描述如何配置消息桥"
#. Tag: para
#: Bridge.xml:96
@@ -242,7 +243,7 @@
"attributes shown. Note that some are commented out for this configuration, "
"since it is not appropriate to specify them all at once. Which ones are "
"specified depends on the configuration you want."
-msgstr ""
+msgstr "下面是一个消息桥配置的例子，它展示了所有的属性。请注意，由于有些配置不适合全部一次被指定，所以它们被注释掉了。这要根据你的需要来取舍。"
#. Tag: programlisting
#: Bridge.xml:100
@@ -341,18 +342,110 @@
" \n"
" </mbean>"
msgstr ""
+"<mbean code=\"org.jboss.jms.server.bridge.BridgeService\"\n"
+" name=\"jboss.messaging:service=Bridge,name=TestBridge\"\n"
+" xmbean-dd=\"xmdesc/Bridge-xmbean.xml\">\n"
+" \n"
+" <!-- The JMS provider loader that is used to lookup the source "
+"destination --> \n"
+" <depends optional-attribute-name=\"SourceProviderLoader\">\n"
+" jboss.messaging:service=JMSProviderLoader,name=JMSProvider</"
+"depends>\n"
+" \n"
+" <!-- The JMS provider loader that is used to lookup the target "
+"destination -->\n"
+" <depends optional-attribute-name=\"TargetProviderLoader\">\n"
+" jboss.messaging:service=JMSProviderLoader,name=JMSProvider</"
+"depends> \n"
+" \n"
+" <!-- The JNDI lookup for the source destination -->\n"
+" <attribute name=\"SourceDestinationLookup\">/queue/A</"
+"attribute> \n"
+" \n"
+" <!-- The JNDI lookup for the target destination -->\n"
+" <attribute name=\"TargetDestinationLookup\">/queue/B</"
+"attribute>\n"
+" \n"
+" <!-- The username to use for the source connection \n"
+" <attribute name=\"SourceUsername\">bob</attribute>\n"
+" -->\n"
+" \n"
+" <!-- The password to use for the source connection\n"
+" <attribute name=\"SourcePassword\">cheesecake</attribute>\n"
+" -->\n"
+" \n"
+" <!-- The username to use for the target connection\n"
+" <attribute name=\"TargetUsername\">mary</attribute>\n"
+" -->\n"
+" \n"
+" <!-- The password to use for the target connection\n"
+" <attribute name=\"TargetPassword\">hotdog</attribute>\n"
+" -->\n"
+" \n"
+" <!-- Optional: The Quality Of Service mode to use, one of:\n"
+" QOS_AT_MOST_ONCE = 0;\n"
+" QOS_DUPLICATES_OK = 1;\n"
+" QOS_ONCE_AND_ONLY_ONCE = 2; -->\n"
+" <attribute name=\"QualityOfServiceMode\">0</attribute>\n"
+" \n"
+" <!-- JMS selector to use for consuming messages from the source\n"
+" <attribute name=\"Selector\">specify jms selector here</"
+"attribute>\n"
+" -->\n"
+" \n"
+" <!-- The maximum number of messages to consume from the source\n"
+" before sending to the target -->\n"
+" <attribute name=\"MaxBatchSize\">5</attribute> \n"
+" \n"
+" <!-- The maximum time to wait (in ms) before sending a batch to the "
+"target\n"
+" even if MaxBatchSize is not exceeded.\n"
+" -1 means wait forever --> \n"
+" <attribute name=\"MaxBatchTime\">-1</attribute>\n"
+" \n"
+" <!-- If consuming from a durable subscription this is the "
+"subscription name\n"
+" <attribute name=\"SubName\">mysub</attribute>\n"
+" -->\n"
+" \n"
+" <!-- If consuming from a durable subscription this is the client ID "
+"to use\n"
+" <attribute name=\"ClientID\">myClientID</attribute>\n"
+" -->\n"
+" \n"
+" <!-- The number of ms to wait between connection retrues in the "
+"event connections\n"
+" to source or target fail -->\n"
+" <attribute name=\"FailureRetryInterval\">5000</"
+"attribute> \n"
+" \n"
+" <!-- The maximum number of connection retries to make in case of "
+"failure,\n"
+" before giving up -1 means try forever-->\n"
+" <attribute name=\"MaxRetries\">-1</attribute>\n"
+"\n"
+" <!-- If true then the message id of the message before bridging "
+"will be added\n"
+" as a header to the message so it is available to the receiver. Can "
+"then be\n"
+" sent as correlation id to correlate in a distributed request-"
+"response -->\n"
+" <attribute name=\"AddMessageIDInHeader\">false</"
+"attribute>\n"
+" \n"
+" </mbean>"
#. Tag: para
#: Bridge.xml:101
#, no-c-format
msgid "We will now discuss each attribute"
-msgstr ""
+msgstr "现在我们逐个来讨论这些属性"
#. Tag: title
#: Bridge.xml:103
#, no-c-format
msgid "SourceProviderLoader"
-msgstr ""
+msgstr "SourceProviderLoader"
#. Tag: para
#: Bridge.xml:104
@@ -360,7 +453,7 @@
msgid ""
"This is the object name of the JMSProviderLoader MBean that the bridge will "
"use to lookup the source connection factory and source destination."
-msgstr ""
+msgstr "这是 JMSProviderLoader MBean 的对象名，消息桥将用它来查找源连接工厂和源目的地。"
#. Tag: para
#: Bridge.xml:107 Bridge.xml:129
@@ -370,7 +463,7 @@
"<filename>jms-ds.xml</filename> - this is the default local "
"JMSProviderLoader. (This would be in <filename>hajndi-jms-ds.xml</filename> "
"in a clustered configuration)"
-msgstr ""
+msgstr "JBoss AS 缺省带有一个 JMSProviderLoader，它部署在 <filename>jms-ds.xml</filename> 文件里 － 这是缺省的本地 JMSProviderLoader（群集配置里的对应文件是 <filename>hajndi-jms-ds.xml</filename>）。"
#. Tag: para
#: Bridge.xml:112
@@ -381,7 +474,7 @@
"JMSProviderLoader MBean instance which references the remote JMS provider, "
"and reference that from this attribute. The bridge would then use that "
"remote JMS provider to contact the source destination"
-msgstr ""
+msgstr "如果源目的地位于不同的服务器上或者甚至对应非 JBoss JMS 提供者，那你可以部署引用远程 JMS 提供者的其他 JMSProviderLoader MBean 实例并用属性引用它。然后消息桥将使用那个远程 JMS 提供者来联系源目的地。"
#. Tag: para
#: Bridge.xml:118 Bridge.xml:140
@@ -392,13 +485,13 @@
"provide a fully functional JMS XA resource implementation that works "
"remotely from the server - it is known that some non JBoss JMS providers do "
"not provide such a resource"
-msgstr ""
+msgstr "请注意，如果你正在使用远程的非 JBoss Messaging 源或目标服务器，且你希望 once and only once 模式的递送，那么该远程的 JMS 提供者必须提供可远程运行的具备完整功能的 JMS XA 资源实现 － 有些非 JBoss JMS 提供者并不提供这样的资源。"
#. Tag: title
#: Bridge.xml:125
#, no-c-format
msgid "TargetProviderLoader"
-msgstr ""
+msgstr "TargetProviderLoader"
#. Tag: para
#: Bridge.xml:126
@@ -406,7 +499,7 @@
msgid ""
"This is the object name of the JMSProviderLoader MBean that the bridge will "
"use to lookup the target connection factory and target destination."
-msgstr ""
+msgstr "这是 JMSProviderLoader MBean 的对象名，消息桥将用它来查找目标连接工厂和目标目的地。"
#. Tag: para
#: Bridge.xml:134
@@ -417,13 +510,13 @@
"JMSProviderLoader MBean instance which references the remote JMS provider, "
"and reference that from this attribute. The bridge would then use that "
"remote JMS provider to contact the target destination"
-msgstr ""
+msgstr "如果你的目标目的地位于不同的服务器上或者甚至对应非 JBoss JMS 提供者，那你可以部署引用远程 JMS 提供者的其他 JMSProviderLoader MBean 实例并用属性引用它。然后消息桥将使用那个远程 JMS 提供者来联系目标目的地。"
#. Tag: title
#: Bridge.xml:147
#, no-c-format
msgid "SourceDestinationLookup"
-msgstr ""
+msgstr "SourceDestinationLookup"
#. Tag: para
#: Bridge.xml:148
@@ -431,19 +524,19 @@
msgid ""
"This is the full JNDI lookup for the source destination using the "
"SourceProviderLoader"
-msgstr ""
+msgstr "这是用于使用 SourceProviderLoader 的源目的地的完整的 JNDI 查找"
#. Tag: para
#: Bridge.xml:150
#, no-c-format
msgid "An example would be /queue/mySourceQueue"
-msgstr ""
+msgstr "例如 /queue/mySourceQueue"
#. Tag: title
#: Bridge.xml:153
#, no-c-format
msgid "TargetDestinationLookup"
-msgstr ""
+msgstr "TargetDestinationLookup"
#. Tag: para
#: Bridge.xml:154
@@ -451,19 +544,19 @@
msgid ""
"This is the full JNDI lookup for the target destination using the "
"TargetProviderLoader"
-msgstr ""
+msgstr "这是用于使用 TargetProviderLoader 的目标目的地的完整的 JNDI 查找"
#. Tag: para
#: Bridge.xml:156
#, no-c-format
msgid "An example would be /topic/myTargetTopic"
-msgstr ""
+msgstr "例如 /topic/myTargetTopic"
#. Tag: title
#: Bridge.xml:159
#, no-c-format
msgid "SourceUsername"
-msgstr ""
+msgstr "SourceUsername"
#. Tag: para
#: Bridge.xml:160
@@ -471,13 +564,13 @@
msgid ""
"This optional attribute is for when you need to specify the username for "
"creating the source connection"
-msgstr ""
+msgstr "这个可选属性是创建源连接时所使用的用户名"
#. Tag: title
#: Bridge.xml:164
#, no-c-format
msgid "SourcePassword"
-msgstr ""
+msgstr "SourcePassword"
#. Tag: para
#: Bridge.xml:165
@@ -485,13 +578,13 @@
msgid ""
"This optional attribute is for when you need to specify the password for "
"creating the source connection"
-msgstr ""
+msgstr "这个可选属性是创建源连接时所使用的密码"
#. Tag: title
#: Bridge.xml:169
#, no-c-format
msgid "TargetUsername"
-msgstr ""
+msgstr "TargetUsername"
#. Tag: para
#: Bridge.xml:170
@@ -499,13 +592,13 @@
msgid ""
"This optional attribute is for when you need to specify the username for "
"creating the target connection"
-msgstr ""
+msgstr "这个可选属性是创建目标连接时所使用的用户名"
#. Tag: title
#: Bridge.xml:174
#, no-c-format
msgid "TargetPassword"
-msgstr ""
+msgstr "TargetPassword"
#. Tag: para
#: Bridge.xml:175
@@ -513,43 +606,43 @@
msgid ""
"This optional attribute is for when you need to specify the password for "
"creating the target connection"
-msgstr ""
+msgstr "这个可选属性是创建源连接时所使用的密码"
#. Tag: title
#: Bridge.xml:179
#, no-c-format
msgid "QualityOfServiceMode"
-msgstr ""
+msgstr "QualityOfServiceMode"
#. Tag: para
#: Bridge.xml:180
#, no-c-format
msgid "This integer represents the desired quality of service mode"
-msgstr ""
+msgstr "这个整型值代表服务模式的级别"
#. Tag: para
#: Bridge.xml:182
#, no-c-format
msgid "Possible values are:"
-msgstr ""
+msgstr "其可能的取值为："
#. Tag: para
#: Bridge.xml:184
#, no-c-format
msgid "QOS_AT_MOST_ONCE = 0"
-msgstr ""
+msgstr "QOS_AT_MOST_ONCE = 0"
#. Tag: para
#: Bridge.xml:187
#, no-c-format
msgid "QOS_DUPLICATES_OK = 1"
-msgstr ""
+msgstr "QOS_DUPLICATES_OK = 1"
#. Tag: para
#: Bridge.xml:190
#, no-c-format
msgid "QOS_ONCE_AND_ONLY_ONCE = 2"
-msgstr ""
+msgstr "QOS_ONCE_AND_ONLY_ONCE = 2"
#. Tag: para
#: Bridge.xml:193
@@ -557,13 +650,13 @@
msgid ""
"Please see <xref linkend=\"bridge.overview\"/> for an explanation of what "
"these mean."
-msgstr ""
+msgstr "具体解释请参考 <xref linkend=\"bridge.overview\"/>。"
#. Tag: title
#: Bridge.xml:197
#, no-c-format
msgid "Selector"
-msgstr ""
+msgstr "Selector"
#. Tag: para
#: Bridge.xml:198
@@ -572,7 +665,7 @@
"This optional attribute can contain a JMS selector expression used for "
"consuming messages from the source destination. Only messages that match the "
"selector expression will be bridged from the source to the target destination"
-msgstr ""
+msgstr "这个可选属性可以包含一个用于从源目的地提取消息的 JMS selector 表达式。只有匹配这个表达式的消息才会从源服务器转移到目标目的地。"
#. Tag: para
#: Bridge.xml:202
@@ -580,7 +673,7 @@
msgid ""
"Please note it is always more performant to apply selectors on source topic "
"subscriptions to source queue consumers."
-msgstr ""
+msgstr "请注意，在源主题订阅上应用 Selector 比在源队列消费者总是具有更好的性能。"
#. Tag: para
#: Bridge.xml:204
@@ -590,12 +683,14 @@
"<ulink url=\"http://java.sun.com/j2ee/1.4/docs/api/javax/jms/Message.html"
"\"></ulink>"
msgstr ""
+"Selector 表达式必须遵循 JMS selector 语法：<ulink url=\"http://java.sun.com/j2ee/1.4/docs/api/javax/jms/Message.html"
+"\"></ulink>"
#. Tag: title
#: Bridge.xml:209
#, no-c-format
msgid "MaxBatchSize"
-msgstr ""
+msgstr "MaxBatchSize"
#. Tag: para
#: Bridge.xml:210
@@ -604,13 +699,13 @@
"This attribute specifies the maximum number of messages to consume from the "
"source destination before sending them in a batch to the target destination. "
"It's value must >= 1"
-msgstr ""
+msgstr "这个属性指定在批量发送至目标目的地前从源目的地提取的消息的最大数量，它的值必须大于 1。"
#. Tag: title
#: Bridge.xml:215
#, no-c-format
msgid "MaxBatchTime"
-msgstr ""
+msgstr "MaxBatchTime"
#. Tag: para
#: Bridge.xml:216
@@ -620,13 +715,13 @@
"sending a batch to target, even if the number of messages consumed has not "
"reached MaxBatchSize. It's value must can be -1 to represent 'wait forever', "
"or >=1 to specify an actual time."
-msgstr ""
+msgstr "这个属性指定在批量发送到目标前等待的最大毫秒数，即使消费的消息数量没有达到 MaxBatchSize。它的值为 -1 则表示“永远等待”，而 >=1 则表示实际的时间。"
#. Tag: title
#: Bridge.xml:222
#, no-c-format
msgid "SubName"
-msgstr ""
+msgstr "SubName"
#. Tag: para
#: Bridge.xml:223
@@ -635,13 +730,13 @@
"If the source destination represents a topic, and you want to consume from "
"the topic using a durable subscription then this attribute represents the "
"durable subscription name"
-msgstr ""
+msgstr "如果源目的地是一个主题，且你想用持久性订阅（Durable Subscription）从这个主题消费消息，那么这个属性就是这个订阅的名字。"
#. Tag: title
#: Bridge.xml:228
#, no-c-format
msgid "ClientID"
-msgstr ""
+msgstr "ClientID"
#. Tag: para
#: Bridge.xml:229
@@ -650,13 +745,13 @@
"If the source destination represents a topic, and you want to consume from "
"the topic using a durable subscription then this attribute represents the "
"the JMS client ID to use when creating/looking up the durable subscription"
-msgstr ""
+msgstr "如果源目的地是一个主题，而你想用一个持久性订阅从这个主题消费消息，那么这个属性就是用来创建/查找该订阅的 JMS 客户 ID。"
#. Tag: title
#: Bridge.xml:235
#, no-c-format
msgid "FailureRetryInterval"
-msgstr ""
+msgstr "FailureRetryInterval"
#. Tag: para
#: Bridge.xml:236
@@ -665,13 +760,13 @@
"This represents the amount of time in ms to wait between trying to recreate "
"connections to the source or target servers when the bridge has detected "
"they have failed"
-msgstr ""
+msgstr "它表示当消息桥检测到连接发生了故障时，在试图与源或目标服务器重建连接前等待的毫秒数。"
#. Tag: title
#: Bridge.xml:241
#, no-c-format
msgid "MaxRetries"
-msgstr ""
+msgstr "MaxRetries"
#. Tag: para
#: Bridge.xml:242
@@ -681,13 +776,13 @@
"the source or target servers when the bridge has detected they have failed. "
"The bridge will give up after trying this number of times. -1 represents "
"'try forever'"
-msgstr ""
+msgstr "它表示当消息桥检测到连接发生了故障时，与源或目标服务器重建连接的最多尝试次数。消息桥在尝试这个次数后将放弃。-1 表示“永远地尝试”。"
#. Tag: title
#: Bridge.xml:248
#, no-c-format
msgid "AddMessageIDInHeader"
-msgstr ""
+msgstr "AddMessageIDInHeader"
#. Tag: para
#: Bridge.xml:249
@@ -699,4 +794,7 @@
"once each message-id will be appended. This enables a distributed request-"
"response pattern to be used"
msgstr ""
+"它如果为 true，那么原始消息的 ID 将附加在发送到目的地的消息的消息头部 JBossMessage."
+"JBOSS_MESSAGING_BRIDGE_MESSAGE_ID_LIST。如果这个消息被多次转发，那么每个 message-id 都将被附加。这使分布式的请求-应答（request-"
+"response）模式被使用。"
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-15 04:51:09 UTC (rev 75821)
+++ projects/docs/enterprise/4.3/Messaging/JBoss_Messaging_User_Guide/zh-CN/Configuration.po 2008-07-15 05:36:16 UTC (rev 75822)
@@ -1,3 +1,4 @@
+# translation of Configuration.po to
# Language zh-CN translations for JBoss_Messaging_User_Guide package.
# Copyright (C) 2008 Free Software Foundation, Inc.
#
@@ -5,15 +6,15 @@
# Xi HUANG <xhuang at redhat.com>, 2008.
msgid ""
msgstr ""
-"Project-Id-Version: JBoss_Messaging_User_Guide 4.3\n"
+"Project-Id-Version: Configuration\n"
"POT-Creation-Date: 2001-02-09 01:25+0100\n"
-"PO-Revision-Date: 2008-07-13 21:49+1000\n"
+"PO-Revision-Date: 2008-07-15 15:35+1000\n"
"Last-Translator: Xi HUANG <xhuang at redhat.com>\n"
-"Language-Team: Chinese Simplified <kde-i18n-doc at lists.kde.org>\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: KAider 0.1\n"
+"X-Generator: KBabel 1.11.4\n"
"Plural-Forms: nplurals=2; plural=n != 1;\n"
#. Tag: title
@@ -420,8 +421,7 @@
#. Tag: para
#: Configuration.xml:61
#, no-c-format
-msgid ""
-"The default JNDI context to use when binding queues. Defaults to /queue."
+msgid "The default JNDI context to use when binding queues. Defaults to /queue."
msgstr "绑定队列时使用的缺省 JNDI 上下文。缺省为 /queue。"
#. Tag: title
@@ -433,8 +433,7 @@
#. Tag: para
#: Configuration.xml:66
#, no-c-format
-msgid ""
-"The default JNDI context to use when binding topics. Defaults to /topic."
+msgid "The default JNDI context to use when binding topics. Defaults to /topic."
msgstr "绑定主题时使用的缺省 JNDI 上下文。缺省为 /topic。"
#. Tag: title
@@ -450,8 +449,7 @@
"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 ""
-"这是 ServerPeer 使用的邮局（Post Office）。通常，你不需要修改这个属性。邮局负责把消息转发至队列并维护地址和队列间的映射。"
+msgstr "这是 ServerPeer 使用的邮局（Post Office）。通常，你不需要修改这个属性。邮局负责把消息转发至队列并维护地址和队列间的映射。"
#. Tag: title
#: Configuration.xml:76
@@ -619,8 +617,7 @@
#. Tag: para
#: Configuration.xml:144
#, no-c-format
-msgid ""
-"The default value is <literal>0</literal> which means there will be no delay."
+msgid "The default value is <literal>0</literal> which means there will be no delay."
msgstr "它的缺省值是 <literal>0</literal>，表示没有延迟。"
#. Tag: para
@@ -716,8 +713,7 @@
#. Tag: para
#: Configuration.xml:183
#, no-c-format
-msgid ""
-"The name of the connection factory to use for pulling messages between nodes."
+msgid "The name of the connection factory to use for pulling messages between nodes."
msgstr ""
#. Tag: para
@@ -817,8 +813,7 @@
#. Tag: para
#: Configuration.xml:222
#, no-c-format
-msgid ""
-"Returns a list of the destinations (queues and topics) currently deployed."
+msgid "Returns a list of the destinations (queues and topics) currently deployed."
msgstr ""
#. Tag: title
@@ -842,8 +837,7 @@
#. Tag: para
#: Configuration.xml:232
#, no-c-format
-msgid ""
-"JBoss Messaging provides statistics for each message counter for each queue."
+msgid "JBoss Messaging provides statistics for each message counter for each queue."
msgstr ""
#. Tag: title
@@ -988,8 +982,7 @@
#. Tag: para
#: Configuration.xml:287
#, no-c-format
-msgid ""
-"The queue is undeployed and then all its data is destroyed from the database."
+msgid "The queue is undeployed and then all its data is destroyed from the database."
msgstr ""
#. Tag: para
@@ -1078,8 +1071,7 @@
#. Tag: para
#: Configuration.xml:330
#, no-c-format
-msgid ""
-"The topic is undeployed and then all its data is destroyed from the database."
+msgid "The topic is undeployed and then all its data is destroyed from the database."
msgstr ""
#. Tag: para
@@ -1107,8 +1099,7 @@
#. Tag: para
#: Configuration.xml:341
#, no-c-format
-msgid ""
-"This operation returns message counters in an easy to display HTML format."
+msgid "This operation returns message counters in an easy to display HTML format."
msgstr ""
#. Tag: title
@@ -1241,8 +1232,7 @@
#. Tag: para
#: Configuration.xml:423
#, no-c-format
-msgid ""
-"It is the job of the post office to route messages to their destination(s)."
+msgid "It is the job of the post office to route messages to their destination(s)."
msgstr ""
#. Tag: para
@@ -1267,8 +1257,7 @@
#. Tag: para
#: Configuration.xml:432
#, no-c-format
-msgid ""
-"The post office also handles the persistence for the mapping of addresses."
+msgid "The post office also handles the persistence for the mapping of addresses."
msgstr ""
#. Tag: para
@@ -1516,8 +1505,7 @@
#. Tag: para
#: Configuration.xml:446
#, no-c-format
-msgid ""
-"The datasource the postoffice should use for persisting its mapping data."
+msgid "The datasource the postoffice should use for persisting its mapping data."
msgstr ""
#. Tag: title
@@ -1628,8 +1616,7 @@
#. Tag: para
#: Configuration.xml:492
#, no-c-format
-msgid ""
-"This returns set containing the node ids of all the nodes in the cluster."
+msgid "This returns set containing the node ids of all the nodes in the cluster."
msgstr ""
#. Tag: title
@@ -2506,8 +2493,7 @@
#. Tag: para
#: Configuration.xml:771
#, no-c-format
-msgid ""
-"The DLQ used for this queue. Overrides any value set on the ServerPeer config"
+msgid "The DLQ used for this queue. Overrides any value set on the ServerPeer config"
msgstr ""
#. Tag: title
@@ -2722,8 +2708,7 @@
#. Tag: para
#: Configuration.xml:862
#, no-c-format
-msgid ""
-"Returns <literal>true</literal> if the queue was created programmatically"
+msgid "Returns <literal>true</literal> if the queue was created programmatically"
msgstr ""
#. Tag: title
@@ -2999,8 +2984,7 @@
#. Tag: para
#: Configuration.xml:985
#, no-c-format
-msgid ""
-"The DLQ used for this topic. Overrides any value set on the ServerPeer config"
+msgid "The DLQ used for this topic. Overrides any value set on the ServerPeer config"
msgstr ""
#. Tag: para
@@ -3022,8 +3006,7 @@
#. Tag: para
#: Configuration.xml:1076
#, no-c-format
-msgid ""
-"Returns <literal>true</literal> if the topic was created programmatically"
+msgid "Returns <literal>true</literal> if the topic was created programmatically"
msgstr ""
#. Tag: para
@@ -3044,8 +3027,7 @@
#. Tag: para
#: Configuration.xml:1098
#, no-c-format
-msgid ""
-"Return a list of the message counters for the subscriptions of this topic."
+msgid "Return a list of the message counters for the subscriptions of this topic."
msgstr ""
#. Tag: title
@@ -3139,8 +3121,7 @@
#. Tag: para
#: Configuration.xml:1137
#, no-c-format
-msgid ""
-"Use this with caution. It will permanently delete all messages from the topic"
+msgid "Use this with caution. It will permanently delete all messages from the topic"
msgstr ""
#. Tag: title
@@ -3250,7 +3231,7 @@
#: Configuration.xml:1196
#, no-c-format
msgid "Configuring Connection Factories"
-msgstr ""
+msgstr "配置连接工厂"
#. Tag: para
#: Configuration.xml:1197
@@ -3258,7 +3239,7 @@
msgid ""
"With the default configuration JBoss Messaging binds two connection "
"factories in JNDI at start-up."
-msgstr ""
+msgstr "在启动时，JBoss Messaging 用缺省的配置在 JNDI 里构建了两个连接工厂。"
#. Tag: para
#: Configuration.xml:1199
@@ -3272,6 +3253,9 @@
"failover or load balancing. This connection factory should be used if you do "
"not require client side automatic failover or load balancing."
msgstr ""
+"第一个连接工厂是缺省的非群集连接工厂，它绑定在下面的 JNDI 上下文里：<literal>/ConnectionFactory, /"
+"XAConnectionFactory, java:/ConnectionFactory, java:/XAConnectionFactory</"
+"literal>。这个连接工厂用来兼容原来针对 JBoss MQ 编写的没有自动失效切换或负载平衡功能的应用程序。如果你不要求客户端的自动失效切换或负载平衡，你应该使用它。"
#. Tag: para
#: Configuration.xml:1208
@@ -3282,6 +3266,9 @@
"ClusteredConnectionFactory, /ClusteredXAConnectionFactory, java:/"
"ClusteredConnectionFactory, java:/ClusteredXAConnectionFactory</literal>."
msgstr ""
+"第二个连接工厂是缺省的群集连接工厂，它绑定在下面的 JNDI 上下文里：<literal>/"
+"ClusteredConnectionFactory, /ClusteredXAConnectionFactory, java:/"
+"ClusteredConnectionFactory, java:/ClusteredXAConnectionFactory</literal>。"
#. Tag: para
#: Configuration.xml:1213
@@ -3295,7 +3282,7 @@
"particular connection factory. Deploying a new connection factory is "
"equivalent with adding a new ConnectionFactory MBean configuration to "
"<filename>connection-factories-service.xml</filename>."
-msgstr ""
+msgstr "你可能想配置其他的连接工厂，例如，你想为连接工厂提供缺省的客户 ID、或者想绑定到不同的 JNDI 位置、或让不同的连接工厂使用不同的传输协议、或选择性地为某个特定的连接工厂启用或禁止负载平衡和/或自动失效切换。在 <filename>connection-factories-service.xml</filename> 里添加新的 ConnectionFactory MBean 配置就可以部署新的连接工厂。"
#. Tag: para
#: Configuration.xml:1222
@@ -3305,6 +3292,8 @@
"<filename>xxx-service.xml</filename> altogether and deploy it in <filename>"
"$JBOSS_HOME/server/messaging/deploy</filename>."
msgstr ""
+"你也可以创建一个完全新的服务部署描述符 <filename>xxx-service.xml</filename> 并部署在 <filename>"
+"$JBOSS_HOME/server/messaging/deploy</filename> 里。"
#. Tag: para
#: Configuration.xml:1225
@@ -3312,13 +3301,13 @@
msgid ""
"Connection factories can support automatic failover and/or load-balancing by "
"setting the corresponding attributes"
-msgstr ""
+msgstr "通过设置相关属性，连接工厂也可以支持自动失效切换和/或负载平衡。"
#. Tag: para
#: Configuration.xml:1227
#, no-c-format
msgid "An example connection factory configuration is presented below:"
-msgstr ""
+msgstr "下面是一个连接工厂配置的例子："
#. Tag: programlisting
#: Configuration.xml:1229
@@ -3371,6 +3360,52 @@
" <attribute name=\"DupsOKBatchSize\">10000</attribute> \n"
" </mbean>"
msgstr ""
+"<mbean code=\"org.jboss.jms.server.connectionfactory.ConnectionFactory\"\n"
+" name=\"jboss.messaging.connectionfactory:service=MyConnectionFactory"
+"\"\n"
+" xmbean-dd=\"xmdesc/ConnectionFactory-xmbean.xml\">\n"
+" <depends optional-attribute-name=\"ServerPeer\">\n"
+" jboss.messaging:service=ServerPeer\n"
+" </depends>\n"
+" <depends optional-attribute-name=\"Connector\">\n"
+" jboss.messaging:service=Connector,transport=bisocket\n"
+" </depends>\n"
+" <depends>jboss.messaging:service=PostOffice</depends>\n"
+"\n"
+" <attribute name=\"JNDIBindings\">\n"
+" <bindings>\n"
+" <binding>/MyConnectionFactory</binding>\n"
+" <binding>/factories/cf</binding>\n"
+" </bindings>\n"
+" </attribute>\n"
+" \n"
+" <attribute name=\"ClientID\">myClientID</attribute>\n"
+"\n"
+" <attribute name=\"SupportsFailover\">true</attribute>\n"
+" \n"
+" <attribute name=\"SupportsLoadBalancing\">false</"
+"attribute> \n"
+" \n"
+" <attribute name=\"LoadBalancingFactory\">org.acme."
+"MyLoadBalancingFactory</attribute>\n"
+" \n"
+" <attribute name=\"PrefetchSize\">1000</attribute> \n"
+"\n"
+" <attribute name=\"SlowConsumers\">false</attribute>\n"
+" \n"
+" <attribute name=\"StrictTck\">true</attribute>\n"
+"\n"
+" <attribute name=\"DefaultTempQueueFullSize\">50000</"
+"attribute>\n"
+" \n"
+" <attribute name=\"DefaultTempQueuePageSize\">1000</"
+"attribute> \n"
+" \n"
+" <attribute name=\"DefaultTempQueueDownCacheSize\">1000</"
+"attribute> \n"
+" \n"
+" <attribute name=\"DupsOKBatchSize\">10000</attribute> \n"
+" </mbean>"
#. Tag: para
#: Configuration.xml:1230
@@ -3388,18 +3423,21 @@
"<literal>Connector</literal> attribute to specify the service name of the "
"connector you wish to use."
msgstr ""
+"上面的例子将创建一个带有预配置客户 ID <literal>myClientID</literal> 的连接工厂并绑定在 JNDI 树的两个地方：<literal>/MyConnectionFactory</literal> 和 "
+"<literal>/factories/cf</literal>。这个连接工厂覆盖了 PreFetchSize、DefaultTempQueueFullSize、"
+"DefaultTempQueuePageSize、DefaultTempQueueDownCacheSize 和 DupsOKBatchSize 的缺省值。它将使用缺省的远程连接器（remoting connector）。要使用不同的远程连接器，你可以修改 <literal>Connector</literal> 属性来指定连接器的服务名。"
#. Tag: title
#: Configuration.xml:1243
#, no-c-format
msgid "MBean attributes of the ConnectionFactory MBean"
-msgstr ""
+msgstr "ConnectionFactory MBean 的 MBean 属性"
#. Tag: title
#: Configuration.xml:1246
#, no-c-format
msgid "ClientID"
-msgstr ""
+msgstr "ClientID"
#. Tag: para
#: Configuration.xml:1247
@@ -3407,25 +3445,25 @@
msgid ""
"Connection factories can be pre-configured with a client id. Any connections "
"created using this connection factory will obtain this client id"
-msgstr ""
+msgstr "连接工厂可用 client id 进行预配置。使用这个连接工厂创建的任何连接都将获得这个 ID。"
#. Tag: title
#: Configuration.xml:1252
#, no-c-format
msgid "JNDIBindings"
-msgstr ""
+msgstr "JNDIBindings"
#. Tag: para
#: Configuration.xml:1253
#, no-c-format
msgid "The list of the JNDI bindings for this connection factory"
-msgstr ""
+msgstr "这个连接工厂使用的 JNDI 绑定的列表"
#. Tag: title
#: Configuration.xml:1257
#, no-c-format
msgid "PrefetchSize"
-msgstr ""
+msgstr "PrefetchSize"
#. Tag: para
#: Configuration.xml:1258
@@ -3438,13 +3476,13 @@
"control, so if you set this to too large a number, then the TCP window size "
"may be hit before the <literal>prefetchSize</literal>, which can cause "
"writes to block."
-msgstr ""
+msgstr "这个参数为消费者（Consumer）流控制指定窗口大小。这个窗口大小决定服务器可以发送到某个消费者而不阻塞的消息数量。每个消费者都维护一个它从中消费的消息缓冲。请注意，TCP 也实现自己的流控制，所以如果你把它设置为过大的值，TCP 窗口大小限制可能在 <literal>prefetchSize</literal> 之前就被突破，这样会导致写阻塞。"
#. Tag: title
#: Configuration.xml:1261
#, no-c-format
msgid "SlowConsumers"
-msgstr ""
+msgstr "SlowConsumers"
#. Tag: para
#: Configuration.xml:1262
@@ -3454,26 +3492,25 @@
"don't buffer any messages since this can prevent them from being consumed by "
"faster consumers. Setting this to true is equivalent to setting "
"<literal>PrefetchSize</literal> to 1."
-msgstr ""
+msgstr "如果存在非常慢的消费者，你可能希望它们不缓冲任何消息，因为这会阻止这些消息被更快的消费者所消费。把它设置为 true 和设置 <literal>PrefetchSize</literal> 为 1 是相等的。"
#. Tag: title
#: Configuration.xml:1266
#, no-c-format
msgid "StrictTck"
-msgstr ""
+msgstr "StrictTck"
#. Tag: para
#: Configuration.xml:1267
#, no-c-format
-msgid ""
-"Set this to true if you want strict JMS behaviour as required by the TCK."
-msgstr ""
+msgid "Set this to true if you want strict JMS behaviour as required by the TCK."
+msgstr "如果你期望 TCK 所要求的严格的 JMS 行为的话，你可以将它设置为 true。"
#. Tag: title
#: Configuration.xml:1271
#, no-c-format
msgid "Temporary queue paging parameters"
-msgstr ""
+msgstr "临时队列的页面参数"
#. Tag: para
#: Configuration.xml:1272
@@ -3486,12 +3523,14 @@
"paging channels for more information on what these values mean. They will "
"default to values of 200000, 2000 and 2000 respectively if ommitted."
msgstr ""
+"DefaultTempQueueFullSize、DefaultTempQueuePageSize、"
+"DefaultTempQueueDownCacheSize 是决定缺省页面参数的可选属性，它们用于连接工厂创建的作用域为临时目的连接。关于这些参数的更多信息，请参考 paging channels 部分的内容。如果忽略的话，它们的缺省值为 200000, 2000 和 2000。"
#. Tag: title
#: Configuration.xml:1281
#, no-c-format
msgid "DupsOKBatchSize"
-msgstr ""
+msgstr "DupsOKBatchSize"
#. Tag: para
#: Configuration.xml:1282
@@ -3500,13 +3539,13 @@
"When using a session with acknowledge mode of DUPS_OK_ACKNOWLEDGE this "
"setting determines how many acknowledgments it will buffer locally before "
"sending. The default value is <literal>2000</literal>"
-msgstr ""
+msgstr "当使用带有 DUPS_OK_ACKNOWLEDGE 确认模式的会话时，设置它可以决定在发送前确认多少次后就在本地进行缓冲。它的缺省值为 <literal>2000</literal>。"
#. Tag: title
#: Configuration.xml:1288
#, no-c-format
msgid "SupportsLoadBalancing"
-msgstr ""
+msgstr "SupportsLoadBalancing"
#. Tag: para
#: Configuration.xml:1289
@@ -3516,7 +3555,7 @@
"installation you can choose whether to enable client side connection load-"
"balancing. This is determined by setting the attribute supportsLoadBalancing "
"on the connection factory."
-msgstr ""
+msgstr "当使用带有群集 JBoss Messaging 安装的连接工厂时，你可以选择是否启用客户端连接的负载平衡。这可以通过设置连接工厂的 supportsLoadBalancing 属性来实现。"
#. Tag: para
#: Configuration.xml:1293
@@ -3526,7 +3565,7 @@
"created with that connection factory will be load-balanced across the nodes "
"of the cluster. Once a connection is created on a particular node, it stays "
"on that node."
-msgstr ""
+msgstr "如果连接工厂启用了负载平衡，那么用它创建的任何连接都将在群集里的节点间进行负载平衡。一旦在某个节点上创建了一个连接，它就会呆在那个节点上。"
#. Tag: para
#: Configuration.xml:1297
@@ -3534,13 +3573,13 @@
msgid ""
"The exact policy that determines how connections are load balanced is "
"determined by the LoadBalancingFactory attribute"
-msgstr ""
+msgstr "连接使用何种策略进行负载平衡是由 LoadBalancingFactory 属性决定的"
#. Tag: para
#: Configuration.xml:1300 Configuration.xml:1322 Configuration.xml:1333
#, no-c-format
msgid "The default value is <literal>false</literal>"
-msgstr ""
+msgstr "它的缺省值为 <literal>false</literal>"
#. Tag: para
#: Configuration.xml:1304
@@ -3550,7 +3589,7 @@
"installation you can choose whether to enable client side automatic "
"failover. This is determined by setting the attribute supportsFailover on "
"the connection factory."
-msgstr ""
+msgstr "当使用带有群集 JBoss Messaging 安装的连接工厂时，你可以选择是否启用客户端自动失效切换。这可以通过设置连接工厂的 supportsFailover 属性来完成。"
#. Tag: para
#: Configuration.xml:1308
@@ -3559,7 +3598,7 @@
"If automatic failover is enabled on a connection factory, then if a "
"connection problem is detected with the connection then JBoss Messaging will "
"automatically and transparently failover to another node in the cluster."
-msgstr ""
+msgstr "如果连接工厂启用了自动失效切换，且某个连接出现了连接问题，JBoss Messaging 将自动和透明地切换至群集里的另外一个节点上。"
#. Tag: para
#: Configuration.xml:1312
@@ -3567,7 +3606,7 @@
msgid ""
"The failover is transparent meaning the user can carry on using the "
"sessions, consumers, producers and connection objects as before."
-msgstr ""
+msgstr "透明的失效切换意味着客户可以象故障发生前一样地使用会话、消费者、生产者和连接对象。"
#. Tag: para
#: Configuration.xml:1315
@@ -3580,12 +3619,14 @@
"caught, the client side code should lookup a new connection factory using "
"HAJNDI and recreate the connection using that."
msgstr ""
+"如果不要求自动失效切换，那可以把这个属性设置为 false。如果禁用了自动失效切换，那么程序代码要在同步 JMS 操作里捕获异常或安装 JMS "
+"ExceptionListener 来异步捕获异常。当某个连接被捕获时，客户端代码应该查找一个使用 HAJNDI 的连接工厂并用它来重新创建连接。"
#. Tag: title
#: Configuration.xml:1325
#, no-c-format
msgid "DisableRemotingChecks"
-msgstr ""
+msgstr "DisableRemotingChecks"
#. Tag: para
#: Configuration.xml:1326
@@ -3597,6 +3638,8 @@
"rarely a good reason to change them. To disable such sanity checking set "
"this to false."
msgstr ""
+"在缺省情况下，在部署一个连接工厂时，JBoss Messaging 将检查对应的 JBoss Remoting Connector 是否具有某些敏感的（\"sensible\"）值。JBoss "
+"Messaging 对这些值非常敏感且很少有修改这些值的时候。要禁用这样的检查，可将其设置为 false。"
#. Tag: para
#: Configuration.xml:1330
@@ -3604,13 +3647,13 @@
msgid ""
"There is rarely a good reason to disable checking. Only do so if you are "
"absolutely sure in what you are doing"
-msgstr ""
+msgstr "我们通常没什么理由禁用这个检查。请在有明确目的时才这么做。"
#. Tag: title
#: Configuration.xml:1336
#, no-c-format
msgid "LoadBalancingFactory"
-msgstr ""
+msgstr "LoadBalancingFactory"
#. Tag: para
#: Configuration.xml:1337
@@ -3620,7 +3663,7 @@
"you can specify how the load balancing is implemented by overriding this "
"attribute. The value must correspond to the name of a class which implements "
"the interface org.jboss.jms.client.plugin.LoadBalancingFactory"
-msgstr ""
+msgstr "如果你在使用带有客户端负载平衡的连接工厂，你可以通过覆盖这个属性来指定实施方法。这个值必须对应实现 org.jboss.jms.client.plugin.LoadBalancingFactory 接口的类名。"
#. Tag: para
#: Configuration.xml:1342
@@ -3630,12 +3673,14 @@
"RoundRobinLoadBalancingFactory, which load balances connections across the "
"cluster in a round-robin fashion"
msgstr ""
+"它的缺省值是 org.jboss.jms.client.plugin."
+"RoundRobinLoadBalancingFactory，这将以 round-robin 模式在群集里平衡连接负载。"
#. Tag: title
#: Configuration.xml:1348
#, no-c-format
msgid "Connector"
-msgstr ""
+msgstr "连接器"
#. Tag: para
#: Configuration.xml:1349
@@ -3643,7 +3688,7 @@
msgid ""
"This specifies which remoting connector this connection factory uses. "
"Different connection factories can use different connectors."
-msgstr ""
+msgstr "它指定连接工厂使用的远程连接器。不同的连接工厂可以使用不同的连接器。"
#. Tag: para
#: Configuration.xml:1352
@@ -3653,13 +3698,13 @@
"connections that use the HTTP transport to communicate to the server and "
"another that creates connections that use the bisocket transport to "
"communicate."
-msgstr ""
+msgstr "例如，你部署的连接工厂可以创建使用 HTTP 传输在服务器和客户端间通信的连接、也可以创建使用双向套接字传输通信的连接。"
#. Tag: title
#: Configuration.xml:1362
#, no-c-format
msgid "Configuring the remoting connector"
-msgstr ""
+msgstr "配置远程连接器"
#. Tag: para
#: Configuration.xml:1363
@@ -3668,7 +3713,7 @@
"JBoss Messaging uses JBoss Remoting for all client to server communication. "
"For full details of what JBoss Remoting is capable of and how it is "
"configured please consult the JBoss Remoting documentation."
-msgstr ""
+msgstr "对于所有的客户端和服务器之间的通信，JBoss Messaging 都使用 JBoss Remoting。关于 JBoss Remoting 的功能和配置，请参考 JBoss Remoting 文档。"
#. Tag: para
#: Configuration.xml:1367
@@ -3677,7 +3722,7 @@
"The default configuration includes a single remoting connector which is used "
"by the single default connection factory. Each connection factory can be "
"configured to use its own connector."
-msgstr ""
+msgstr "缺省的配置包括单一的远程连接器，它被单一的缺省连接工厂使用。你可以配置每个连接工厂都使用自己的连接器。"
#. Tag: para
#: Configuration.xml:1370
@@ -3689,7 +3734,7 @@
"initiated from the client side. This means it works well in typical firewall "
"scenarios where only inbound connections are allowed on the server. Or where "
"onlu outbound connections are allowed from the client."
-msgstr ""
+msgstr "缺省的连接器使用远程双向套接字传输（bisocket transport）。双向套接字传输基于 TCP 套接字，它只在服务器端侦听和接受连接。也就是说，连接总是从客户端发起。这意味着它适合于典型的防火墙环境里，因为此时只允许服务器上的转入连接。或者说只允许客户端的转出连接。"
#. Tag: para
#: Configuration.xml:1377
@@ -3697,7 +3742,7 @@
msgid ""
"The bisocket transport can be configured to use SSL where a higher level of "
"security is required."
-msgstr ""
+msgstr "如果需要更高级别的安全性，我们可以配置双向套接字传输使用 SSL。"
#. Tag: para
#: Configuration.xml:1379
@@ -3711,19 +3756,19 @@
"Please note this transport will not be as performant as the bisocket "
"transport due to the nature of polling and the HTTP protocl. Also please "
"note it is not designed for high load situations."
-msgstr ""
+msgstr "另外一种被支持的传输协是 HTTP 传输。它使用 HTTP 协议在服务器和客户端之间通信。客户端通过定期地轮询服务器来接收数据。这种传输特别适合于在客户端和服务器之间存在防火墙的情况，此时只允许服务器上的转入 HTTP 通信。请注意，这种传输不具有和双向传输相同的性能，这是由于轮询的性质以及 HTTP 协议的采用。也请注意它不是为高负载环境设计的。"
#. Tag: para
#: Configuration.xml:1388
#, no-c-format
msgid "No other remoting transports are currently supported by JBoss Messaging"
-msgstr ""
+msgstr "JBoss Messaging 目前不支持其他远程传输模式。"
#. Tag: para
#: Configuration.xml:1390
#, no-c-format
msgid "You can look at remoting configuration under:"
-msgstr ""
+msgstr "你可以在这里查看远程配置："
#. Tag: para
#: Configuration.xml:1391
@@ -3732,12 +3777,14 @@
"<JBoss>/server/<YourMessagingServer>/deploy/jboss-messaging.sar/"
"remoting-bisocket-service.xml"
msgstr ""
+"<JBoss>/server/<YourMessagingServer>/deploy/jboss-messaging.sar/"
+"remoting-bisocket-service.xml"
#. Tag: para
#: Configuration.xml:1392
#, no-c-format
msgid "Here is an example bisocket remoting configuration:"
-msgstr ""
+msgstr "下面是一个关于双向远程传输的配置示例："
#. Tag: programlisting
#: Configuration.xml:1393
@@ -3809,6 +3856,71 @@
" </handlers>\n"
" </config>"
msgstr ""
+"<config>\n"
+" <invoker transport=\"bisocket\">\n"
+" \n"
+" <!-- There should be no reason to change these parameters "
+"- warning!\n"
+" Changing them may stop JBoss Messaging working correctly "
+"--> \n"
+" <attribute name=\"marshaller\" isParam=\"true\">org."
+"jboss.jms.wireformat.JMSWireFormat</attribute>\n"
+" <attribute name=\"unmarshaller\" isParam=\"true\">org."
+"jboss.jms.wireformat.JMSWireFormat</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\">4457</"
+"attribute>\n"
+" <attribute name=\"clientSocketClass\" isParam=\"true\">"
+"org.jboss.jms.client.remoting.ClientSocketWrapper</attribute>\n"
+" <attribute name=\"serverSocketClass\" isParam=\"true\">"
+"org.jboss.jms.server.remoting.ServerSocketWrapper</attribute>\n"
+" <attribute name=\"numberOfCallRetries\" isParam=\"true"
+"\">1</attribute>\n"
+" <attribute name=\"pingFrequency\" isParam=\"true"
+"\">214748364</attribute>\n"
+" <attribute name=\"pingWindowFactor\" isParam=\"true"
+"\">10</attribute>\n"
+" <attribute name=\"onewayThreadPool\">org.jboss.jms."
+"server.remoting.DirectThreadPool</attribute>\n"
+" \n"
+" <!-- Periodicity of client pings. Server window by default "
+"is twice this figure --> \n"
+" <attribute name=\"clientLeasePeriod\" isParam=\"true"
+"\">10000</attribute>\n"
+"\n"
+" <!-- Number of seconds to wait for a connection in the "
+"client pool to become free -->\n"
+" <attribute name=\"numberOfRetries\" isParam=\"true"
+"\">10</attribute>\n"
+"\n"
+" <!-- Max Number of connections in client pool. This should "
+"be significantly higher than\n"
+" the max number of sessions/consumers you expect -->\n"
+" <attribute name=\"clientMaxPoolSize\" isParam=\"true"
+"\">200</attribute>\n"
+" \n"
+" <!-- Use these parameters to specify values for binding "
+"and connecting control connections to \n"
+" work with your firewall/NAT configuration\n"
+" <attribute name=\"secondaryBindPort\">xyz</"
+"attribute> \n"
+" <attribute name=\"secondaryConnectPort\">abc</"
+"attribute> \n"
+" -->\n"
+" \n"
+" </invoker>\n"
+" <handlers>\n"
+" <handler subsystem=\"JMS\">org.jboss.jms.server."
+"remoting.JMSServerInvocationHandler</handler>\n"
+" </handlers>\n"
+" </config>"
#. Tag: para
#: Configuration.xml:1394
@@ -3817,7 +3929,7 @@
"Please note that some of the attributes should not be changed unless you "
"know exactly what you are doing. We will discuss the attributes that you may "
"have a good reason to change:"
-msgstr ""
+msgstr "请注意，除非你有明确的目的，否则不要修改其中一些属性。我们将讨论你可能需要修改的属性："
#. Tag: para
#: Configuration.xml:1398
@@ -3831,7 +3943,7 @@
"default) close a client if it does not receive a heartbeat in 2 * "
"clientLeasePeriod ms. The actual factor gets automatically resized according "
"to system load. The value is in milliseconds. The defaut value is 10000 ms."
-msgstr ""
+msgstr "clientLeasePeriod - 客户端定期地往服务器发送 heartbeat 来告知它处于活动状态。如果服务器在一段时间后没有接收到 heartbeat，那么它将关掉连接并删除这个会话对应的所有服务器上的资源。clientLeasePeriod 决定了发送 heartbeat 的间隔。如果服务器在 2 * clientLeasePeriod 毫秒后还没有收到 heartbeat 信息，它缺省将关闭这个客户连接。实际的因子会根据系统负载自动进行调节。这个值以毫秒为单位。它的缺省值是 10000 毫秒。"
#. Tag: para
#: Configuration.xml:1401
@@ -3843,7 +3955,7 @@
"concurrently accessing the server from a client and you are experiencing "
"issues due to not being able to obtain connections from the pool, you may "
"want to consider increasing this value."
-msgstr ""
+msgstr "numberOfRetries - 它对应 JBoss Remoting 在等待客户连接池有空闲的连接时阻塞的时间（秒）。如果有数目众多的会话并行地访问服务器，且你遇到不能从连接池获得连接的问题，那么你就可以考虑增大这个值。"
#. Tag: para
#: Configuration.xml:1404
@@ -3854,7 +3966,7 @@
"sessions concurrently accessing the server from a client and you are "
"experiencing issues due to not being able to obtain connections from the "
"pool in a timely manner, you may want to consider increasing this value."
-msgstr ""
+msgstr "clientMaxPoolSize - JBoss Remoting 维护一个客户端的对应服务请求的 TCP 连接池。如果有数目众多的会话并行地访问服务器，且你遇到不能及时地从连接池获得连接的问题，那么你就可以考虑增大这个值。"
#. Tag: para
#: Configuration.xml:1407
@@ -3865,7 +3977,7 @@
"firewall you may want to specify a particular value for this according to "
"your firewall configuration. This is the address the secondary ServerSocket "
"binds to"
-msgstr ""
+msgstr "secondaryBindPort - 双向传输使用控制连接（control connection）在服务器和客户端之间传递控制消息。如果你想在防火墙后工作，你可能需要按照防火墙配置为这个连接指定特殊的值。它是第二个 ServerSocket 所绑定的地址。"
#. Tag: para
#: Configuration.xml:1410
@@ -3873,7 +3985,7 @@
msgid ""
"secondaryConnectPort - This is the port the client uses to connect. You may "
"want to specify this to allow clients to work with NAT routers."
-msgstr ""
+msgstr "secondaryConnectPort - 这是客户端用户连接的端口。你可能希望指定它来允许客户使用 NAT 路由器。"
#. Tag: para
#: Configuration.xml:1413
@@ -3881,7 +3993,7 @@
msgid ""
"maxPoolSize - This is the number of threads used on the server side to "
"service requests."
-msgstr ""
+msgstr "maxPoolSize - 这是服务器端用于处理请求的线程数量。"
#. Tag: para
#: Configuration.xml:1417
@@ -3889,7 +4001,7 @@
msgid ""
"By default JBoss Messaging binds to ${jboss.bind.address} which can be "
"defined by: ./run.sh -c <yourconfig> -b yourIP."
-msgstr ""
+msgstr "在缺省情况下，JBoss Messaging 绑定到 ${jboss.bind.address}，它可用 ./run.sh -c <yourconfig> -b yourIP 进行定义。"
#. Tag: para
#: Configuration.xml:1419
@@ -3897,7 +4009,7 @@
msgid ""
"You can change remoting-bisocket-service.xml if you want for example use a "
"different communication port."
-msgstr ""
+msgstr "如果你想使用不同的通信端口，你可以修改 remoting-bisocket-service.xml。"
#. Tag: para
#: Configuration.xml:1421
@@ -3909,12 +4021,14 @@
"secondaryConnectPort. Changing them can cause JBoss Messaging to stop "
"functioning correctly."
msgstr ""
+"除了 clientLeasePeriod、clientMaxPoolSize、maxRetries、numberOfRetries、secondaryBindPort 和 "
+"secondaryConnectPort 以外，我们通常不需修改 bisocket 或 sslbisocket 连接器配置里的其他值。修改这些值可能导致 JBoss Messaging 不能正常运行。"
#. Tag: title
#: Configuration.xml:1427
#, no-c-format
msgid "ServiceBindingManager"
-msgstr ""
+msgstr "ServiceBindingManager"
#. Tag: para
#: Configuration.xml:1428
@@ -3926,6 +4040,9 @@
"the ServiceBindingManager xml file exactly matches that in remoting-bisocket-"
"service.xml."
msgstr ""
+"如果你要使用 JBoss AS ServiceBindingManager 来提供带有不同端口范围俄的不同服务器，你必须确保 ServiceBindingManager xml 文件里的 JBoss Messaging 部分里的 JBoss "
+"Messaging 远程配置完全符合 remoting-bisocket-"
+"service.xml 里的配置。"
#. Tag: para
#: Configuration.xml:1433
@@ -3935,5 +4052,5 @@
"example bindings in the AS distribution may well be out of date. It is "
"therefore imperative that the relevant sections are overwritten with the "
"remoting configuration from the JBM distribution."
-msgstr ""
+msgstr "如果你在较旧版本的 JBAS 里使用更新版本的 JBM，那么 AS 发行版本里的例子可能是过期的。因此相关部分急需用 JBM 发行版本里的远程配置进行覆盖。"
More information about the jboss-cvs-commits
mailing list