[jboss-cvs] JBossAS SVN: r101438 - projects/docs/enterprise/5.0/Administration_And_Configuration_Guide/zh-CN.
jboss-cvs-commits at lists.jboss.org
jboss-cvs-commits at lists.jboss.org
Wed Feb 24 22:39:15 EST 2010
Author: xhuang at jboss.com
Date: 2010-02-24 22:39:15 -0500 (Wed, 24 Feb 2010)
New Revision: 101438
Modified:
projects/docs/enterprise/5.0/Administration_And_Configuration_Guide/zh-CN/Messaging.po
Log:
update
Modified: projects/docs/enterprise/5.0/Administration_And_Configuration_Guide/zh-CN/Messaging.po
===================================================================
--- projects/docs/enterprise/5.0/Administration_And_Configuration_Guide/zh-CN/Messaging.po 2010-02-25 03:28:46 UTC (rev 101437)
+++ projects/docs/enterprise/5.0/Administration_And_Configuration_Guide/zh-CN/Messaging.po 2010-02-25 03:39:15 UTC (rev 101438)
@@ -8,7 +8,7 @@
"Project-Id-Version: Clustering_Guide_JNDI\n"
"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
"POT-Creation-Date: 2009-12-09T13:49:18\n"
-"PO-Revision-Date: 2010-02-16 10:35+1000\n"
+"PO-Revision-Date: 2010-02-25 10:56+1000\n"
"Last-Translator: Xi HUANG <xhuang at redhat.com>\n"
"Language-Team: <en at li.org>\n"
"MIME-Version: 1.0\n"
@@ -89,7 +89,7 @@
#. Tag: para
#, no-c-format
msgid "The JBoss Messaging service configuration is spread among several configuration files. Depending on the functionality provided by the services it configures, the configuration data is distributed between <filename><JBOSS_HOME>/server/<configuration>/deploy/messaging-service.xml, remoting-service.xml, connection-factories-service.xml, destinations-service.xml and xxx-persistence-service.xml</filename> (where <literal>xxx</literal> is the name of your database). The default will be <filename>hsqldb-persistence-service.xml</filename> for the hsqldb database."
-msgstr ""
+msgstr "JBoss Messaging 服务配置跨越多个配置文件。根据它配置的服务所提供的功能，配置数据分布在 <filename><JBOSS_HOME>/server/<configuration>/deploy/messaging-service.xml, remoting-service.xml, connection-factories-service.xml, destinations-service.xml 和 xxx-persistence-service.xml</filename> 里（这里的 <literal>xxx</literal> 是数据库的名称）。 hsqldb 数据库的缺省值是 <filename>hsqldb-persistence-service.xml</filename>。"
#. Tag: title
#, fuzzy, no-c-format
@@ -99,12 +99,12 @@
#. Tag: para
#, no-c-format
msgid "SecurityStore is a pluggable object, and it has a default implementation in <filename>messaging-service.xml</filename>:"
-msgstr ""
+msgstr "SecurityStore 是一个可插拔的对象，它在 <filename>messaging-service.xml</filename> 里有一个缺省的实现："
#. Tag: para
#, no-c-format
msgid "This implementation points the ServerPeer to <code>jboss.messaging:service=SecurityStore</code>, which is defined in the <filename>messaging-jboss-beans.xml</filename> file."
-msgstr ""
+msgstr "这个实现把 ServerPeer 指向 <code>jboss.messaging:service=SecurityStore</code>，这是在 <filename>messaging-jboss-beans.xml</filename> 文件李定义的。"
#. Tag: title
#, fuzzy, no-c-format
@@ -114,7 +114,7 @@
#. Tag: para
#, no-c-format
msgid "The following are SecurityStore attributes from the <filename>messaging-jboss-beans.xml</filename> file above."
-msgstr ""
+msgstr "下面是 <filename>messaging-jboss-beans.xml</filename> 文件里的 SecurityStore 属性："
#. Tag: title
#, no-c-format
@@ -124,7 +124,7 @@
#. Tag: para
#, no-c-format
msgid "Default security configuration is used when the security configuration for a specific queue or topic has not been overridden in the destination's deployment descriptor. It has exactly the same syntax and semantics as in JBossMQ."
-msgstr ""
+msgstr "当没有在目的地的部署描述符里覆盖特殊队列或主题的安全配置时，缺省的安全配置将被使用。它和在 JBossMQ 里一样具有相同的语法和语义。"
#. Tag: para
#, no-c-format
@@ -134,7 +134,7 @@
#. Tag: para
#, no-c-format
msgid "If the read attribute is true then that role will be able to read (create consumers, receive messaages or browse) destinations by default. If the write attribute is true then that role will be able to write (create producers or send messages) to destinations by default. If the create attribute is true then that role will be able to create durable subscriptions on topics by default."
-msgstr ""
+msgstr "如果 read 属性为 true，则该角色缺省可以读取目的地（创建消费者、接收或浏览消息）。如果 write 属性为 true，则该角色缺省可以写入目的地（创建生产者或发送消息）。如果 create 属性为 true，那么该角色缺省可以在主题上创建可持久的订阅（durable subscription）。"
#. Tag: title
#, no-c-format
@@ -154,7 +154,7 @@
#. Tag: para
#, no-c-format
msgid "This defines how the SecurityStore will authenticate the sucker user (<literal>JBM.SUCKER</literal>)."
-msgstr ""
+msgstr "这定义了 SecurityStore 如何验证 sucker 用户（<literal>JBM.SUCKER</literal>）。"
#. Tag: title
#, fuzzy, no-c-format
@@ -164,7 +164,7 @@
#. Tag: para
#, no-c-format
msgid "The <classname>ServerPeer</classname> is the heart of the JBoss Messaging JMS. All JBoss Messaging services are rooted at the server peer and the server's configuration resides in the <filename>messaging-service.xml</filename> configuration file. An example of a Server Peer configuration is presented below, though not all values for the server peer's attributes are specified in the example."
-msgstr ""
+msgstr "<classname>ServerPeer</classname> 是 JBoss Messaging JMS 的核心。所有的 JBoss Messaging 服务都位于服务器端点的根目录下且服务的配置处于 <filename>messaging-service.xml</filename> 配置文件里。下面是一个服务器端点（Server Peer）的配置，在这个例子里并没有列出所有的属性值。"
#. Tag: title
#, fuzzy, no-c-format
@@ -174,52 +174,52 @@
#. Tag: para
#, no-c-format
msgid "This section discusses the MBean attributes of the ServerPeer MBean."
-msgstr ""
+msgstr "本部分讨论了 ServerPeer MBean 的 MBean 属性。"
#. Tag: title
#, no-c-format
msgid "ServerPeerID"
-msgstr ""
+msgstr "ServerPeerID"
#. Tag: para
#, no-c-format
msgid "The <classname>ServerPeerID</classname> is the unique ID of the server peer that every node you deploy <emphasis>must</emphasis> have. This applies whether the different nodes form a cluster, or are only linked via a message bridge. The ID must be a valid integer."
-msgstr ""
+msgstr "classname>ServerPeerID</classname> 是你部署的每个节点都<emphasis>必须</emphasis>具有的唯一的服务器端点 ID。无论是群集里的还是通过消息桥链接的不同节点，这都适用。这个 ID 必须是一个有效的整数。"
#. Tag: para
#, no-c-format
msgid "The scope of <classname>ServerPeerID</classname> is currently from 0 to 255. <!-- Future releases will see this enlarged to 1023 -->"
-msgstr ""
+msgstr "<classname>ServerPeerID</classname> 的范围是 0 到 255（以后版本会改为 0 到 1023）。"
#. Tag: title
#, no-c-format
msgid "DefaultQueueJNDIContext"
-msgstr ""
+msgstr "DefaultQueueJNDIContext"
#. Tag: para
#, no-c-format
msgid "The default JNDI context to use when binding queues. Defaults to <literal>/queue</literal>."
-msgstr ""
+msgstr "绑定队列时使用的缺省 JNDI 上下文。缺省为 <literal>/queue</literal>。"
#. Tag: title
#, no-c-format
msgid "DefaultTopicJNDIContext"
-msgstr ""
+msgstr "DefaultTopicJNDIContext"
#. Tag: para
#, no-c-format
msgid "The default JNDI context to use when binding topics.wa Defaults to <literal>/topic</literal>."
-msgstr ""
+msgstr "绑定主题时使用的缺省 JNDI。缺省为 <literal>/topic</literal>。"
#. Tag: title
#, no-c-format
msgid "PostOffice"
-msgstr ""
+msgstr "PostOffice"
#. Tag: para
#, no-c-format
msgid "This is the post office that the ServerPeer uses. You will not normally need 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 使用的邮局。你通常不需要修改这个属性。邮局负责把消息路由到队列并维护地址和队列间的映射。"
#. Tag: title
#, fuzzy, no-c-format
@@ -229,112 +229,112 @@
#. Tag: para
#, no-c-format
msgid "This is the name of the default DLQ (Dead Letter Queue) the server peer will use for destinations. The DLQ can be overridden on a per destination basis - see the destination MBean configuration for more details. A DLQ is a special destination where messages are sent when the server has attempted to deliver them unsuccessfully more than a certain number of times. If the DLQ is not specified at all then the message will be removed after the maximum number of delivery attempts. The maximum number of delivery attempts can be specified using the attribute DefaultMaxDeliveryAttempts for a global default or individually on a per destination basis."
-msgstr ""
+msgstr "这是服务器端点用于目的地的缺省 DLQ（Dead Letter Queue）的名称。对每个目的地可以使用不同的 DLQ - 更多信息请参考 destination MBean 配置。DLQ 是一个特殊的目的地，当服务器试图递送消息时失败了规定的次数后，消息将被递送到这里。如果没有指定 DLQ，那么在尝试指定的次数后消息将被删除。递送的最多尝试次数可以用 DefaultMaxDeliveryAttempts 来指定，这可以作为全局缺省值或者是对于每个目的地进行设置。"
#. Tag: title
#, no-c-format
msgid "DefaultMaxDeliveryAttempts"
-msgstr ""
+msgstr "DefaultMaxDeliveryAttempts"
#. Tag: para
#, no-c-format
msgid "The default for the maximum number of times delivery of a message will be attempted before sending the message to the DLQ, if configured."
-msgstr ""
+msgstr "如果进行了配置，在发往 DLQ 之前，消息将进行所指定的最多次数的递送尝试。"
#. Tag: para
#, no-c-format
msgid "The default value is 10.This value can also be overridden on a per destination basis."
-msgstr ""
+msgstr "缺省值是10。这个值也可以根据每个目的地进行覆盖。"
#. Tag: title
#, no-c-format
msgid "DefaultExpiryQueue"
-msgstr ""
+msgstr "DefaultExpiryQueue"
#. Tag: para
#, no-c-format
msgid "This is the name of the default expiry queue the server peer will use for destinations. The expiry can be overridden on a per destination basis - see the destination MBean configuration for more details. An expiry queue is a special destination where messages are sent when they have expired. Message expiry is determined by the value of Message::getJMSExpiration() If the expiry queue is not specified at all then the message will be removed after it is expired."
-msgstr ""
+msgstr "这是服务器端将用于目的地的缺省 expiry 队列的名称。过期时间可以根据每个目的地进行覆盖 - 更多细节可以参看 destination MBean 的配置。expiry 队列是一个特殊的目的地，当消息过期时就会被送到这里。消息是否过期是由 Message::getJMSExpiration() 的值决定的，如果没有指定 expiry 队列，消息在过期后将被删除。"
#. Tag: title
#, no-c-format
msgid "DefaultRedeliveryDelay"
-msgstr ""
+msgstr "DefaultRedeliveryDelay"
#. Tag: para
#, no-c-format
msgid "When redelivering a message after failure of previous delivery it is often beneficial to introduce a delay perform redelivery in order to prevent thrashing of delivery-failure, delivery-failure etc."
-msgstr ""
+msgstr "当在前次递送失败后再重新递送消息时，引入一个延迟机制以防止递送失败的拥塞通常是有益的。"
#. Tag: para
#, no-c-format
msgid "The default value is 0 which means there will be no delay."
-msgstr ""
+msgstr "缺省值是 0，表示没有延迟。"
#. Tag: para
#, no-c-format
msgid "Change this if your application could benefit with a delay before redelivery. This value can also be overridden on a per destination basis."
-msgstr ""
+msgstr "如果你的应用程序可以受益于在重新递送前采用延迟，你可以修改它。这个值也可以根据每个目的地进行设置。"
#. Tag: title
#, no-c-format
msgid "MessageCounterSamplePeriod"
-msgstr ""
+msgstr "MessageCounterSamplePeriod"
#. Tag: para
#, no-c-format
msgid "Periodically the server will query each queue to gets its statistics. This is the period."
-msgstr ""
+msgstr "服务器将定期查询每个队列以获取统计信息。这里是时间间隔。"
#. Tag: para
#, no-c-format
msgid "The default value is 10000 milliseconds."
-msgstr ""
+msgstr "缺省值是 10000 毫秒。"
#. Tag: title
#, no-c-format
msgid "FailoverStartTimeout"
-msgstr ""
+msgstr "FailoverStartTimeout"
#. Tag: para
#, no-c-format
msgid "The maximum number of milliseconds the client will wait for failover to start on the server side when a problem is detected."
-msgstr ""
+msgstr "当检测到问题时，客户等待失效切换启动的时间，以毫秒未单位。"
#. Tag: para
#, no-c-format
msgid "The default value is 60000 (one minute)."
-msgstr ""
+msgstr "缺省值是 60000（1分钟）。"
#. Tag: title
#, no-c-format
msgid "FailoverCompleteTimeout"
-msgstr ""
+msgstr "FailoverCompleteTimeout"
#. Tag: para
#, no-c-format
msgid "The maximum number of milliseconds the client will wait for failover to complete on the server side after it has started. The default value is 300000 (five minutes)."
-msgstr ""
+msgstr "客户等待服务器端的失效切换完成前所等待的最长时间（毫秒）。缺省值是 30000（5分钟）。"
#. Tag: title
#, no-c-format
msgid "DefaultMessageCounterHistoryDayLimit"
-msgstr ""
+msgstr "DefaultMessageCounterHistoryDayLimit"
#. Tag: para
#, no-c-format
msgid "JBoss Messaging provides a message counter history which shows the number of messages arriving on each queue of a certain number of days. This attribute represents the maxiumum number of days for which to store message counter history. It can be overridden on a per destination basis."
-msgstr ""
+msgstr "JBoss Messaging 提供了一个消息计数器历史，它显示了一段时间里消息到达每个队列的消息数量。这个属性代表了存储消息技术器历史的最大天数。它可以根据每个目的地进行覆盖。"
#. Tag: title
#, no-c-format
msgid "ClusterPullConnectionFactory"
-msgstr ""
+msgstr "ClusterPullConnectionFactory"
#. Tag: para
#, no-c-format
msgid "The name of the connection factory to use for pulling messages between nodes. If you wish to turn off message sucking between queues altogether, but retain failover, then you can ommit this attribute altogether."
-msgstr ""
+msgstr "在节点获取消息所使用的连接工厂的名称。如果你想关闭队列间的消息停留而保持失效切换，你可以忽略这个属性。"
#. Tag: title
#, no-c-format
@@ -344,7 +344,7 @@
#. Tag: para
#, no-c-format
msgid "If true, then strict JMS ordering is preserved in the cluster. See the cluster configurations section for more details. Default is false."
-msgstr ""
+msgstr "如果未 true，那么群集里将实行严格的 JMS 顺序。更多细节请参考群集配置部分的内容。它缺省为 false。"
#. Tag: title
#, no-c-format
More information about the jboss-cvs-commits
mailing list