[jboss-cvs] JBossAS SVN: r76020 - 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
Sun Jul 20 06:07:00 EDT 2008
Author: xhuang at jboss.com
Date: 2008-07-20 06:07:00 -0400 (Sun, 20 Jul 2008)
New Revision: 76020
Modified:
projects/docs/enterprise/4.3/Messaging/JBoss_Messaging_User_Guide/zh-CN/Configuration.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-20 08:46:14 UTC (rev 76019)
+++ projects/docs/enterprise/4.3/Messaging/JBoss_Messaging_User_Guide/zh-CN/Configuration.po 2008-07-20 10:07:00 UTC (rev 76020)
@@ -8,13 +8,13 @@
msgstr ""
"Project-Id-Version: Configuration\n"
"POT-Creation-Date: 2001-02-09 01:25+0100\n"
-"PO-Revision-Date: 2008-07-17 15:29+1000\n"
+"PO-Revision-Date: 2008-07-20 20:06+1000\n"
"Last-Translator: Xi HUANG <xhuang at redhat.com>\n"
-"Language-Team: <en at li.org>\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: KBabel 1.11.4\n"
+"X-Generator: KAider 0.1\n"
"Plural-Forms: nplurals=2; plural=n != 1;\n"
#. Tag: title
@@ -2304,7 +2304,7 @@
#: Configuration.xml:688
#, no-c-format
msgid "UseNDBFailoverStrategy"
-msgstr ""
+msgstr "UseNDBFailoverStrategy"
#. Tag: para
#: Configuration.xml:689
@@ -2318,7 +2318,7 @@
"happens then the SQL statement will be re-executed. However any further "
"error is ignored because an assumption is made that the error is due to the "
"previous transaction being committed successfully."
-msgstr ""
+msgstr "当在群集的数据库环境里运行时，某些数据库如 MySQL，可能在提交数据库事务时失败。如果在提交阶段数据库节点停止运行了，那么就无法获知该事务的最后状态。如果设置了 <literal>UseNDBFailoverStrategy</literal> 为 true，那么相关 SQL 语句将被重新执行。然而，任何进一步的错误将被忽略，这是因为我们假设这个错误是由于前面成功提交的事务所引起的。"
#. Tag: para
#: Configuration.xml:694
@@ -2326,13 +2326,13 @@
msgid ""
"By default the value of the attribute <literal>UseNDBFailoverStrategy</"
"literal> is set to <literal>false.</literal>"
-msgstr ""
+msgstr "<literal>UseNDBFailoverStrategy</literal> 的缺省值是 <literal>false</literal>。"
#. Tag: title
#: Configuration.xml:701
#, no-c-format
msgid "Configuring the JMS user manager"
-msgstr ""
+msgstr "配置 JMS User Manager"
#. Tag: para
#: Configuration.xml:702
@@ -2341,13 +2341,13 @@
"The JMS user manager handles the mapping of pre-configured client IDs to "
"users and also managers the user and role tables which may or may not be "
"used depending on which login module you have configured"
-msgstr ""
+msgstr "JMS user manager 处理预配置的客户 ID 和用户的映射，它也管理用户和角色表（其是否被使用取决于你所配置的登录模块）。"
#. Tag: para
#: Configuration.xml:705
#, no-c-format
msgid "Here is an example JMSUserManager configuration"
-msgstr ""
+msgstr "下面是一个配置 JMSUserManager 的例子"
#. Tag: programlisting
#: Configuration.xml:706
@@ -2382,12 +2382,40 @@
" ]]></attribute>\n"
" </mbean>"
msgstr ""
+"<mbean code=\"org.jboss.jms.server.plugin.JDBCJMSUserManagerService\"\n"
+" name=\"jboss.messaging:service=JMSUserManager\"\n"
+" xmbean-dd=\"xmdesc/JMSUserManager-xmbean.xml\">\n"
+" <depends>jboss.jca:service=DataSourceBinding,name=DefaultDS</"
+"depends>\n"
+" <depends optional-attribute-name=\"TransactionManager\">\n"
+" jboss:service=TransactionManager\n"
+" </depends>\n"
+" <attribute name=\"DataSource\">java:/DefaultDS</"
+"attribute>\n"
+" <attribute name=\"CreateTablesOnStartup\">true</"
+"attribute>\n"
+" <attribute name=\"SqlProperties\"><![CDATA[\n"
+" CREATE_USER_TABLE=CREATE TABLE JBM_USER (USER_ID VARCHAR(32) "
+"NOT NULL,\n"
+" PASSWD VARCHAR(32) NOT NULL, CLIENTID VARCHAR(128),\n"
+" PRIMARY KEY(USER_ID)) ENGINE = INNODB\n"
+" CREATE_ROLE_TABLE=CREATE TABLE JBM_ROLE (ROLE_ID VARCHAR(32) "
+"NOT NULL,\n"
+" USER_ID VARCHAR(32) NOT NULL, PRIMARY KEY(USER_ID, ROLE_ID))\n"
+" ENGINE = INNODB\n"
+" SELECT_PRECONF_CLIENTID=SELECT CLIENTID FROM JBM_USER WHERE "
+"USER_ID=?\n"
+" POPULATE.TABLES.1=INSERT INTO JBM_USER (USER_ID,PASSWD,"
+"CLIENTID)\n"
+" VALUES ('dilbert','dogbert','dilbert-id')\n"
+" ]]></attribute>\n"
+" </mbean>"
#. Tag: title
#: Configuration.xml:708
#, no-c-format
msgid "MBean attributes of the JMSUserManager MBean"
-msgstr ""
+msgstr "JMSUserManager MBean 的 MBean 属性"
#. Tag: para
#: Configuration.xml:712
@@ -2398,7 +2426,7 @@
"indexes) already exist a <literal>SQLException</literal> will be thrown by "
"the JDBC driver and ignored by the Persistence Manager, allowing it to "
"continue."
-msgstr ""
+msgstr "如果你希望 JMS user manager 试图在启动时创建表（和索引），请设置它为 <literal>true</literal>。如果这个表（或索引）已经存在，那么 JDBC 驱动将抛出 <literal>SQLException</literal> 而 Persistence Manager 会忽略这个异常来使其继续运行。"
#. Tag: para
#: Configuration.xml:736
@@ -2407,19 +2435,19 @@
"Default user and role data can also be specified here. Any data to be "
"inserted must be specified with property names starting with "
"<literal>POPULATE.TABLES</literal> as in the above example."
-msgstr ""
+msgstr "缺省的用户和角色数据也可以在这里指定。如上例一样，任何被插入的数据必须用名称以 <literal>POPULATE.TABLES</literal> 开始的属性来指定。"
#. Tag: title
#: Configuration.xml:746
#, no-c-format
msgid "Configuring Destinations"
-msgstr ""
+msgstr "配置目的地"
#. Tag: title
#: Configuration.xml:748
#, no-c-format
msgid "Pre-configured destinations"
-msgstr ""
+msgstr "预配置的目的地"
#. Tag: para
#: Configuration.xml:749
@@ -2429,7 +2457,7 @@
"will be deployed during the server start up. The file that contains "
"configuration for these destinations is <filename>destinations-service.xml</"
"filename>. A section of this file is listed below:"
-msgstr ""
+msgstr "JBoss Messaging 带有一套缺省的预配置目的地，它将在服务器启动过程中被部署。针对这些目的地的包含配置信息的文件是 <filename>destinations-service.xml</filename>。下面是这个文件的一部分内容："
#. Tag: programlisting
#: Configuration.xml:754
@@ -2594,60 +2622,218 @@
" </mbean>\n"
"...."
msgstr ""
+"<!--\n"
+" The Default Dead Letter Queue. This destination is a dependency of an "
+"EJB MDB container.\n"
+" -->\n"
+"\n"
+" <mbean code=\"org.jboss.jms.server.destination.QueueService\"\n"
+" name=\"jboss.messaging.destination:service=Queue,name=DLQ\"\n"
+" xmbean-dd=\"xmdesc/Queue-xmbean.xml\">\n"
+" <depends optional-attribute-name=\"ServerPeer\">\n"
+" jboss.messaging:service=ServerPeer\n"
+" </depends>\n"
+" <depends>jboss.messaging:service=PostOffice</depends>\n"
+" </mbean>\n"
+"\n"
+"\n"
+" <mbean code=\"org.jboss.jms.server.destination.TopicService\"\n"
+" name=\"jboss.messaging.destination:service=Topic,name=testTopic\"\n"
+" xmbean-dd=\"xmdesc/Topic-xmbean.xml\">\n"
+" <depends optional-attribute-name=\"ServerPeer\">\n"
+" jboss.messaging:service=ServerPeer\n"
+" </depends>\n"
+" <depends>jboss.messaging:service=PostOffice</depends>\n"
+" <attribute name=\"SecurityConfig\">\n"
+" <security>\n"
+" <role name=\"guest\" read=\"true\" write=\"true\"/>\n"
+" <role name=\"publisher\" read=\"true\" write=\"true\" create="
+"\"false\"/>\n"
+" <role name=\"durpublisher\" read=\"true\" write=\"true\" "
+"create=\"true\"/>\n"
+" </security>\n"
+" </attribute>\n"
+" </mbean>\n"
+"\n"
+" <mbean code=\"org.jboss.jms.server.destination.TopicService\"\n"
+" name=\"jboss.messaging.destination:service=Topic,name=securedTopic\"\n"
+" xmbean-dd=\"xmdesc/Topic-xmbean.xml\">\n"
+" <depends optional-attribute-name=\"ServerPeer\">\n"
+" jboss.messaging:service=ServerPeer\n"
+" </depends>\n"
+" <depends>jboss.messaging:service=PostOffice</depends>\n"
+" <attribute name=\"SecurityConfig\">\n"
+" <security>\n"
+" <role name=\"publisher\" read=\"true\" write=\"true\" create="
+"\"false\"/>\n"
+" </security>\n"
+" </attribute>\n"
+" </mbean>\n"
+"\n"
+"\n"
+" <mbean code=\"org.jboss.jms.server.destination.QueueService\"\n"
+" name=\"jboss.messaging.destination:service=Queue,name=testQueue\"\n"
+" xmbean-dd=\"xmdesc/Queue-xmbean.xml\">\n"
+" <depends optional-attribute-name=\"ServerPeer\">\n"
+" jboss.messaging:service=ServerPeer\n"
+" </depends>\n"
+" <depends>jboss.messaging:service=PostOffice</depends>\n"
+" <attribute name=\"SecurityConfig\">\n"
+" <security>\n"
+" <role name=\"guest\" read=\"true\" write=\"true\"/>\n"
+" <role name=\"publisher\" read=\"true\" write=\"true\" create="
+"\"false\"/>\n"
+" <role name=\"noacc\" read=\"false\" write=\"false\" create="
+"\"false\"/>\n"
+" </security>\n"
+" </attribute>\n"
+" </mbean>\n"
+"\n"
+" <mbean code=\"org.jboss.jms.server.destination.QueueService\"\n"
+" name=\"jboss.messaging.destination:service=Queue,name=A\"\n"
+" xmbean-dd=\"xmdesc/Queue-xmbean.xml\">\n"
+" <depends optional-attribute-name=\"ServerPeer\">\n"
+" jboss.messaging:service=ServerPeer\n"
+" </depends>\n"
+" <depends>jboss.messaging:service=PostOffice</depends>\n"
+" </mbean>\n"
+"\n"
+"\n"
+" <!-- It's possible for indiviual queues and topics to use a specific "
+"queue for\n"
+" an expiry or DLQ -->\n"
+"\n"
+" <mbean code=\"org.jboss.jms.server.destination.QueueService\"\n"
+" name=\"jboss.messaging.destination:service=Queue,name=PrivateDLQ\"\n"
+" xmbean-dd=\"xmdesc/Queue-xmbean.xml\">\n"
+" <depends optional-attribute-name=\"ServerPeer\">\n"
+" jboss.messaging:service=ServerPeer\n"
+" </depends>\n"
+" <depends>jboss.messaging:service=PostOffice</depends>\n"
+" </mbean>\n"
+"\n"
+" <mbean code=\"org.jboss.jms.server.destination.QueueService\"\n"
+" name=\"jboss.messaging.destination:service=Queue,"
+"name=PrivateExpiryQueue\"\n"
+" xmbean-dd=\"xmdesc/Queue-xmbean.xml\">\n"
+" <depends optional-attribute-name=\"ServerPeer\">\n"
+" jboss.messaging:service=ServerPeer\n"
+" </depends>\n"
+" <depends>jboss.messaging:service=PostOffice</depends>\n"
+" </mbean>\n"
+"\n"
+" <mbean code=\"org.jboss.jms.server.destination.QueueService\"\n"
+" name=\"jboss.messaging.destination:service=Queue,"
+"name=QueueWithOwnDLQAndExpiryQueue\"\n"
+" xmbean-dd=\"xmdesc/Queue-xmbean.xml\">\n"
+" <depends optional-attribute-name=\"ServerPeer\">\n"
+" jboss.messaging:service=ServerPeer\n"
+" </depends>\n"
+" <depends>jboss.messaging:service=PostOffice</depends>\n"
+" <attribute name=\"DLQ\">\n"
+" jboss.messaging.destination:service=Queue,name=PrivateDLQ\n"
+" </attribute>\n"
+" <attribute name=\"ExpiryQueue\">\n"
+" jboss.messaging.destination:service=Queue,"
+"name=PrivateExpiryQueue\n"
+" </attribute>\n"
+" </mbean>\n"
+"\n"
+" <mbean code=\"org.jboss.jms.server.destination.TopicService\"\n"
+" name=\"jboss.messaging.destination:service=Topic,"
+"name=TopicWithOwnDLQAndExpiryQueue\"\n"
+" xmbean-dd=\"xmdesc/Topic-xmbean.xml\">\n"
+" <depends optional-attribute-name=\"ServerPeer\">\n"
+" jboss.messaging:service=ServerPeer\n"
+" </depends>\n"
+" <depends>jboss.messaging:service=PostOffice</depends>\n"
+" <attribute name=\"DLQ\">\n"
+" jboss.messaging.destination:service=Queue,name=PrivateDLQ\n"
+" </attribute>\n"
+" <attribute name=\"ExpiryQueue\">\n"
+" jboss.messaging.destination:service=Queue,"
+"name=PrivateExpiryQueue\n"
+" </attribute>\n"
+" </mbean>\n"
+"\n"
+"\n"
+" <mbean code=\"org.jboss.jms.server.destination.TopicService\"\n"
+" name=\"jboss.messaging.destination:service=Topic,"
+"name=TopicWithOwnRedeliveryDelay\"\n"
+" xmbean-dd=\"xmdesc/Topic-xmbean.xml\">\n"
+" <depends optional-attribute-name=\"ServerPeer\">\n"
+" jboss.messaging:service=ServerPeer\n"
+" </depends>\n"
+" <depends>jboss.messaging:service=PostOffice</depends>\n"
+" <attribute name=\"RedeliveryDelay\">5000</attribute>\n"
+" </mbean>\n"
+"\n"
+"\n"
+" <mbean code=\"org.jboss.jms.server.destination.TopicService\"\n"
+" name=\"jboss.messaging.destination:service=Topic,"
+"name=testDistributedTopic\"\n"
+" xmbean-dd=\"xmdesc/Topic-xmbean.xml\">\n"
+" <depends optional-attribute-name=\"ServerPeer\">\n"
+" jboss.messaging:service=ServerPeer\n"
+" </depends>\n"
+" <depends>jboss.messaging:service=PostOffice</depends>\n"
+" <attribute name=\"Clustered\">true</attribute>\n"
+" </mbean>\n"
+"...."
#. Tag: title
#: Configuration.xml:758
#, no-c-format
msgid "Configuring queues"
-msgstr ""
+msgstr "配置队列"
#. Tag: title
#: Configuration.xml:760
#, no-c-format
msgid "Attributes of the Queue MBean"
-msgstr ""
+msgstr "Queue MBean 的属性"
#. Tag: title
#: Configuration.xml:762 Configuration.xml:976
#, no-c-format
msgid "Name"
-msgstr ""
+msgstr "Name"
#. Tag: para
#: Configuration.xml:763
#, no-c-format
msgid "The name of the queue"
-msgstr ""
+msgstr "队列的名称"
#. Tag: title
#: Configuration.xml:766 Configuration.xml:980
#, no-c-format
msgid "JNDIName"
-msgstr ""
+msgstr "JNDIName"
#. Tag: para
#: Configuration.xml:767
#, no-c-format
msgid "The JNDI name where the queue is bound"
-msgstr ""
+msgstr "队列绑定的 JNDI 名称"
#. Tag: title
#: Configuration.xml:770 Configuration.xml:984
#, no-c-format
msgid "<title>DLQ</title>"
-msgstr ""
+msgstr "<title>DLQ</title>"
#. Tag: para
#: Configuration.xml:771
#, no-c-format
msgid "The DLQ used for this queue. Overrides any value set on the ServerPeer config"
-msgstr ""
+msgstr "用于这个队列的 DLQ。它将覆盖 ServerPeer 配置里的任何值。"
#. Tag: title
#: Configuration.xml:775 Configuration.xml:989
#, no-c-format
msgid "ExpiryQueue"
-msgstr ""
+msgstr "ExpiryQueue"
#. Tag: para
#: Configuration.xml:776
@@ -2655,13 +2841,13 @@
msgid ""
"The Expiry queue used for this queue. Overrides any value set on the "
"ServerPeer config"
-msgstr ""
+msgstr "用于这个队列的过期队列（Expiry Queue）。它将覆盖 ServerPeer 配置里的任何值。"
#. Tag: title
#: Configuration.xml:780 Configuration.xml:994
#, no-c-format
msgid "RedeliveryDelay"
-msgstr ""
+msgstr "RedeliveryDelay"
#. Tag: para
#: Configuration.xml:781
@@ -2669,13 +2855,13 @@
msgid ""
"The redelivery delay to be used for this queue. Overrides any value set on "
"the ServerPeer config"
-msgstr ""
+msgstr "这个队列使用的重递送延迟。它将覆盖 ServerPeer 配置里的任何值。"
#. Tag: title
#: Configuration.xml:785 Configuration.xml:999
#, no-c-format
msgid "MaxDeliveryAttempts"
-msgstr ""
+msgstr "MaxDeliveryAttempts"
#. Tag: para
#: Configuration.xml:786 Configuration.xml:1000
@@ -2685,13 +2871,13 @@
"sending the message to the DLQ, if configured. If set to -1 (the default), "
"the value from the ServerPeer config is used. Any other setting overrides "
"the value set on the ServerPeer config."
-msgstr ""
+msgstr "在把消息发送到 DLQ 之前，尝试递送消息的最大次数。如果为 -1（缺省值），ServerPeer 配置里值将被使用。任何其他值将覆盖 ServerPeer 配置里的值。"
#. Tag: title
#: Configuration.xml:793 Configuration.xml:1007
#, no-c-format
msgid "Destination Security Configuration"
-msgstr ""
+msgstr "目的地的安全性配置"
#. Tag: para
#: Configuration.xml:794 Configuration.xml:1008
@@ -2701,7 +2887,7 @@
"allowed to read, write and create on the destination. It has exactly the "
"same syntax and semantics as the security configuration in JBossMQ "
"destinations."
-msgstr ""
+msgstr "<literal>SecurityConfig</literal> - 允许你决定哪些角色可以在目的地读、写和创建。它具有和 JBossMQ 目的地的安全配置完全相同的语法。"
#. Tag: para
#: Configuration.xml:798 Configuration.xml:1012
@@ -2712,7 +2898,7 @@
"literal> element can contain multiple <literal><role></literal> "
"elements. Each <literal><role></literal> element defines the access "
"for that particular role."
-msgstr ""
+msgstr "<literal>SecurityConfig</literal> 元素里应该包含一个 <literal><security></literal> 元素。而 <literal><security></literal> 元素可以包含多个 <literal><role></literal> 元素。每个 <literal><role></literal> 元素都定义特定角色的访问权限。"
#. Tag: para
#: Configuration.xml:804 Configuration.xml:1018
@@ -2721,7 +2907,7 @@
"If the <literal>read</literal> attribute is <literal>true</literal> then "
"that role will be able to read (create consumers, receive messaages or "
"browse) this destination."
-msgstr ""
+msgstr "如果 <literal>read</literal> 属性为 <literal>true</literal>，那么这个角色可以读取（创建消费者、接收消息或浏览消息）目的地。"
#. Tag: para
#: Configuration.xml:808 Configuration.xml:1022
@@ -2730,7 +2916,7 @@
"If the <literal>write</literal> attribute is <literal>true</literal> then "
"that role will be able to write (create producers or send messages) to this "
"destination."
-msgstr ""
+msgstr "如果 <literal>write</literal> 属性为 <literal>true</literal>，那么该角色可以写这个目的地（创建生产者或发送消息）。"
#. Tag: para
#: Configuration.xml:811 Configuration.xml:1025
@@ -2738,7 +2924,7 @@
msgid ""
"If the <literal>create</literal> attribute is <literal>true</literal> then "
"that role will be able to create durable subscriptions on this destination."
-msgstr ""
+msgstr "如果 <literal>create</literal> 属性为 <literal>true</literal>，那么该角色可以在这个目的地上创建持久性订阅。"
#. Tag: para
#: Configuration.xml:814 Configuration.xml:1028
@@ -2747,13 +2933,13 @@
"Note that the security configuration for a destination is optional. If a "
"<literal>SecurityConfig</literal> element is not specifed then the default "
"security configuration from the Server Peer will be used."
-msgstr ""
+msgstr "请注意目的地的安全性配置是可选的。如果没有指定 <literal>SecurityConfig</literal> 元素，那么 Server Peer 里的缺省安全配置将被使用。"
#. Tag: title
#: Configuration.xml:820 Configuration.xml:1034
#, no-c-format
msgid "Destination paging parameters"
-msgstr ""
+msgstr "目的地的页面参数"
#. Tag: para
#: Configuration.xml:821 Configuration.xml:1035
@@ -2761,7 +2947,7 @@
msgid ""
"'Pageable Channels' are a sophisticated new feature available in JBoss "
"Messaging."
-msgstr ""
+msgstr "'Pageable Channels' 是 JBoss Messaging 里的一个复杂的新功能。"
#. Tag: para
#: Configuration.xml:823 Configuration.xml:1037
@@ -2770,7 +2956,7 @@
"If your application needs to support very large queues or subscriptions "
"containing potentially millions of messages, then it's not possible to store "
"them all in memory at once."
-msgstr ""
+msgstr "如果你的应用程序需要支持超大的对列或可能包含数百万条消息的订阅，那么一次性进行存储就不可能。"
#. Tag: para
#: Configuration.xml:826 Configuration.xml:1040
@@ -2782,7 +2968,7 @@
"and from storage transparently in blocks, allowing queues and subscriptions "
"to grow to very large sizes without any performance degradation as channel "
"size increases."
-msgstr ""
+msgstr "JBoss Messaging 没有解决这个问题，但它可以让你指定可以一次性存储在内存里的每个队列或主题的消息的最大个数。JBoss Messaging 然后以块的形式透明地将这些消息分页，允许队列和订阅非常大而不影响性能。"
#. Tag: para
#: Configuration.xml:833 Configuration.xml:1047
@@ -2790,13 +2976,13 @@
msgid ""
"This has been tested with in excess of 10 million 2K messages on very basic "
"hardware and has the potential to scale to much larger number of messages."
-msgstr ""
+msgstr "这已经在基本的硬件上使用超过一千万零两千条消息进行了测试，且有可能扩展至更大的数目。"
#. Tag: para
#: Configuration.xml:836 Configuration.xml:1050
#, no-c-format
msgid "The individual parameters are:"
-msgstr ""
+msgstr "其各个参数为："
#. Tag: para
#: Configuration.xml:837 Configuration.xml:1051
@@ -2806,7 +2992,7 @@
"the queue or topic subscriptions in memory at any one time. The actual queue "
"or subscription can hold many more messages than this but these are paged to "
"and from storage as necessary as messages are added or consumed."
-msgstr ""
+msgstr "<literal>FullSize</literal> - 这是内存里的队列或主题订阅在任何时刻可容纳的最大消息数目。实际的队列或订阅可以容纳比这更多的消息，因为在添加或消费消息时可以按需要将这些消息分页至存储里。"
#. Tag: para
#: Configuration.xml:842 Configuration.xml:1056
@@ -2815,7 +3001,7 @@
"<literal>PageSize</literal> - When loading messages from the queue or "
"subscrition this is the maximum number of messages to pre-load in one "
"operation."
-msgstr ""
+msgstr "<literal>PageSize</literal> - 当从队列或订阅加载消息时，这是在某个操作里可以预加载的最大消息数目。"
#. Tag: para
#: Configuration.xml:845 Configuration.xml:1059
@@ -2826,7 +3012,7 @@
"This enables the write to occur as a single operation thus aiding "
"performance. This setting determines the max number of messages that the "
"Down Cache will hold before they are flushed to storage."
-msgstr ""
+msgstr "<literal>DownCacheSize</literal> - 当把消息从队列里分页至存储里时，在实际上写入前它们首先进入一个 \"Down Cache\" 里。这使写入成为单个操作，因此提高了性能。这个设置决定了 Down Cache 在冲刷消息至存储前可容纳的消息的最大数目。"
#. Tag: para
#: Configuration.xml:851 Configuration.xml:1065
@@ -2835,7 +3021,7 @@
"If no values for <literal>FullSize</literal>, <literal>PageSize</literal>, "
"or <literal>DownCacheSize</literal> are specified they will default to "
"values 75000, 2000, 2000 respectively."
-msgstr ""
+msgstr "如果没有指定 <literal>FullSize</literal>、<literal>PageSize</literal> 或 <literal>DownCacheSize</literal>，它们的缺省值将分别是 75000、2000、2000。"
#. Tag: para
#: Configuration.xml:855 Configuration.xml:1069
@@ -2844,25 +3030,25 @@
"If you want to specify the paging parameters used for temporary queues then "
"you need to specify them on the appropriate connection factory. See "
"connection factory configuration for details."
-msgstr ""
+msgstr "如果你向指定用于临时队列的页面参数，那么你需要在合适的连接工厂上对它们进行指定。详情请参考连接工厂的配置。"
#. Tag: title
#: Configuration.xml:861 Configuration.xml:1075
#, no-c-format
msgid "CreatedProgrammatically"
-msgstr ""
+msgstr "CreatedProgrammatically"
#. Tag: para
#: Configuration.xml:862
#, no-c-format
msgid "Returns <literal>true</literal> if the queue was created programmatically"
-msgstr ""
+msgstr "如果队列是在程序里创建的话，返回 <literal>true</literal>"
#. Tag: title
#: Configuration.xml:866
#, no-c-format
msgid "MessageCount"
-msgstr ""
+msgstr "MessageCount"
#. Tag: para
#: Configuration.xml:867
@@ -2870,13 +3056,13 @@
msgid ""
"Returns the total number of messages in the queue = number not being "
"delivered + number being delivered + number being scheduled"
-msgstr ""
+msgstr "返回队列里的消息总数，它等于正在递送的消息数目 + 未递送的消息数目 + 正被调度的消息数目。"
#. Tag: title
#: Configuration.xml:872
#, no-c-format
msgid "ScheduledMessageCount"
-msgstr ""
+msgstr "ScheduledMessageCount"
#. Tag: para
#: Configuration.xml:873
@@ -2884,7 +3070,7 @@
msgid ""
"Returns the number of scheduled messages in the queue. This is the number of "
"messages scheduled to be delivered at a later date."
-msgstr ""
+msgstr "返回队列里已调度的消息的数目。这些消息预定在以后的时间进行递送。"
#. Tag: para
#: Configuration.xml:876
@@ -2894,7 +3080,7 @@
"message and specify the earliest time at which it will be delivered. E.g. "
"you can send a message now, but the message won't actually be delivered "
"until 2 hours time."
-msgstr ""
+msgstr "调度递送是 JBoss Messaging 的一个功能，你可以发送消息并指定递送的最早时间。例如，你可以现在就发送一条消息，但这个消息实际上会在两小时后被递送。"
#. Tag: para
#: Configuration.xml:880
@@ -2902,7 +3088,7 @@
msgid ""
"To do this, you just need to set the following header in the message before "
"sending:"
-msgstr ""
+msgstr "要实现这一点，你只需要在消息里设置下面的消息头部信息："
#. Tag: programlisting
#: Configuration.xml:882
@@ -2918,12 +3104,21 @@
" \n"
" prod.send(msg);"
msgstr ""
+"long now = System.currentTimeMillis();\n"
+" \n"
+" Message msg = sess.createMessage(); \n"
+" \n"
+" msg.setLongProperty(JBossMessage."
+"JMS_JBOSS_SCHEDULED_DELIVERY_PROP_NAME,\n"
+" now + 1000 * 60 * 60 * 2);\n"
+" \n"
+" prod.send(msg);"
#. Tag: title
#: Configuration.xml:885 Configuration.xml:1080
#, no-c-format
msgid "MaxSize"
-msgstr ""
+msgstr "MaxSize"
#. Tag: para
#: Configuration.xml:886
More information about the jboss-cvs-commits
mailing list