[jboss-cvs] JBossAS SVN: r75939 - 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
Thu Jul 17 02:20:31 EDT 2008
Author: xhuang at jboss.com
Date: 2008-07-17 02:20:31 -0400 (Thu, 17 Jul 2008)
New Revision: 75939
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-17 06:16:53 UTC (rev 75938)
+++ projects/docs/enterprise/4.3/Messaging/JBoss_Messaging_User_Guide/zh-CN/Configuration.po 2008-07-17 06:20:31 UTC (rev 75939)
@@ -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-16 15:19+1000\n"
+"PO-Revision-Date: 2008-07-17 15:29+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
@@ -1816,6 +1816,9 @@
"use the in-VM Hypersonic database instance that comes by default with any "
"JBossAS instance."
msgstr ""
+"\"persistent\" 服务的配置以 <filename>xxx-"
+"persistence-service.xml</filename> 文件的形式分组，其中的 xxx 对应数据库名称。在缺省情况下，JBoss Messaging 附带一个 <filename>hsqldb-"
+"persistence-service.xml</filename> 文件，它配置任何 JBossAS 实例缺省使用的 in-VM Hypersonic 数据库。"
#. Tag: para
#: Configuration.xml:587
@@ -1825,7 +1828,7 @@
"However, it must be stressed that Hypersonic should not be used in a "
"production environment, mainly due to its limited support for transaction "
"isolation, and its propensity to behave erratically under high load."
-msgstr ""
+msgstr "Persistence Manager 缺省使用 Hypersonic。然而，我们需要强调的是，Hypersonic 不应该用在产品环境里，这是因为它只有限地支持事务隔离，且在高负荷下表现不稳定。"
#. Tag: para
#: Configuration.xml:589
@@ -1835,6 +1838,8 @@
"\">Critique of Hypersonic</ulink> wiki page outlines some of the well-known "
"issues occuring when using this database."
msgstr ""
+"<ulink url=\"http://wiki.jboss.org/wiki/Wiki.jsp?page=ConfigJBossMQDB"
+"\">Critique of Hypersonic</ulink> wiki 页面概述了使用这个数据库的一些众所周知的问题。"
#. Tag: para
#: Configuration.xml:594
@@ -1849,6 +1854,11 @@
"persistence-service.xml</filename> configuration files are available in the "
"<filename>examples/config</filename> directory of the release bundle."
msgstr ""
+"JBoss Messaging 也附带用于 MySQL、Oracle、PostgreSQL、Sybase 和 MS SQL Server 的 Persistence Manager 配置。示例的 <filename>mysql-persistence-service.xml</filename>、<filename>ndb-"
+"persistence-service.xml</filename>、<filename>oracle-persistence-service."
+"xml</filename>、<filename>postgres-persistence-service.xml</filename>、 "
+"<filename>sybase-persistence-service.xml</filename> 和 <filename>mssql-"
+"persistence-service.xml</filename> 文件位于 <filename>examples/config</filename> 目录之下。"
#. Tag: para
#: Configuration.xml:604
@@ -1860,7 +1870,7 @@
"standard SQL for the DML so writing a JDBC Persistence Manager configuration "
"for another database is usually only a fairly simple matter of changing DDL "
"in the configuration which is likely to be different for different databases."
-msgstr ""
+msgstr "我们鼓励用户贡献自己的配置文件，我们将在认证之前进行详尽测试。JDBC Persistence Manager 被设计成对 DML 使用标准的 SQL ，所以为其他数据库编写 JDBC Persistence Manager 配置通常只需要修改其中的 DDL（对于不同的数据库，这些语句很可能有差别）就可以了。"
#. Tag: para
#: Configuration.xml:611
@@ -1868,13 +1878,13 @@
msgid ""
"JBoss Messaging also ships with a 'Null Persistence Manager' config - this "
"can be used when you don't want any persistence at all."
-msgstr ""
+msgstr "JBoss Messaging 也带有一个 'Null Persistence Manager' 配置 － 它可以在你根本不需要任何持久化时使用。"
#. Tag: para
#: Configuration.xml:613
#, no-c-format
msgid "The default Hypersonic persistence configuration file is listed below:"
-msgstr ""
+msgstr "下面是缺省的 Hypersonic persistence 配置文件："
#. Tag: programlisting
#: Configuration.xml:615
@@ -2015,12 +2025,146 @@
" \n"
" </mbean>"
msgstr ""
+"<mbean code=\"org.jboss.messaging.core.jmx.JDBCPersistenceManagerService"
+"\"\n"
+" name=\"jboss.messaging:service=PersistenceManager\"\n"
+" xmbean-dd=\"xmdesc/JDBCPersistenceManager-xmbean.xml\">\n"
+" \n"
+" <depends>jboss.jca:service=DataSourceBinding,name=DefaultDS</"
+"depends>\n"
+" \n"
+" <depends optional-attribute-name=\"TransactionManager\">jboss:"
+"service=TransactionManager</depends>\n"
+" \n"
+" <!-- The datasource to use for the persistence manager -->\n"
+" \n"
+" <attribute name=\"DataSource\">java:/DefaultDS</"
+"attribute> \n"
+" \n"
+" <!-- If true will attempt to create tables and indexes on every "
+"start-up -->\n"
+" \n"
+" <attribute name=\"CreateTablesOnStartup\">true</"
+"attribute>\n"
+" \n"
+" <!-- If true then will use JDBC batch updates -->\n"
+" \n"
+" <attribute name=\"UsingBatchUpdates\">true</attribute>\n"
+" \n"
+" <attribute name=\"SqlProperties\"><![CDATA[\n"
+" CREATE_DUAL=CREATE TABLE JBM_DUAL (DUMMY INTEGER, PRIMARY KEY (DUMMY)) "
+"ENGINE = INNODB\n"
+" CREATE_MESSAGE_REFERENCE=CREATE TABLE JBM_MSG_REF (CHANNEL_ID BIGINT, "
+"MESSAGE_ID BIGINT, TRANSACTION_ID BIGINT, STATE CHAR(1), ORD BIGINT, "
+"PAGE_ORD BIGINT, DELIVERY_COUNT INTEGER, SCHED_DELIVERY BIGINT, PRIMARY KEY"
+"(CHANNEL_ID, MESSAGE_ID)) ENGINE = INNODB\n"
+" CREATE_IDX_MESSAGE_REF_TX=CREATE INDEX JBM_MSG_REF_TX ON JBM_MSG_REF "
+"(TRANSACTION_ID)\n"
+" CREATE_IDX_MESSAGE_REF_ORD=CREATE INDEX JBM_MSG_REF_ORD ON JBM_MSG_REF "
+"(ORD)\n"
+" CREATE_IDX_MESSAGE_REF_PAGE_ORD=CREATE INDEX JBM_MSG_REF_PAGE_ORD ON "
+"JBM_MSG_REF (PAGE_ORD)\n"
+" CREATE_IDX_MESSAGE_REF_MESSAGE_ID=CREATE INDEX JBM_MSG_REF_MESSAGE_ID ON "
+"JBM_MSG_REF (MESSAGE_ID)\n"
+" CREATE_IDX_MESSAGE_REF_SCHED_DELIVERY=CREATE INDEX "
+"JBM_MSG_REF_SCHED_DELIVERY ON JBM_MSG_REF (SCHED_DELIVERY)\n"
+" CREATE_MESSAGE=CREATE TABLE JBM_MSG (MESSAGE_ID BIGINT, RELIABLE CHAR(1), "
+"EXPIRATION BIGINT, TIMESTAMP BIGINT, PRIORITY TINYINT, TYPE TINYINT, HEADERS "
+"MEDIUMBLOB, PAYLOAD LONGBLOB, PRIMARY KEY (MESSAGE_ID)) ENGINE = INNODB\n"
+" CREATE_IDX_MESSAGE_TIMESTAMP=CREATE INDEX JBM_MSG_REF_TIMESTAMP ON "
+"JBM_MSG (TIMESTAMP)\n"
+" CREATE_TRANSACTION=CREATE TABLE JBM_TX (NODE_ID INTEGER, TRANSACTION_ID "
+"BIGINT, BRANCH_QUAL VARBINARY(254), FORMAT_ID INTEGER, GLOBAL_TXID VARBINARY"
+"(254), PRIMARY KEY (TRANSACTION_ID)) ENGINE = INNODB\n"
+" CREATE_COUNTER=CREATE TABLE JBM_COUNTER (NAME VARCHAR(255), NEXT_ID "
+"BIGINT, PRIMARY KEY(NAME)) ENGINE = INNODB\n"
+" INSERT_DUAL=INSERT INTO JBM_DUAL VALUES (1)\n"
+" CHECK_DUAL=SELECT 1 FROM JBM_DUAL\n"
+" INSERT_MESSAGE_REF=INSERT INTO JBM_MSG_REF (CHANNEL_ID, MESSAGE_ID, "
+"TRANSACTION_ID, STATE, ORD, PAGE_ORD, DELIVERY_COUNT, SCHED_DELIVERY) VALUES "
+"(?, ?, ?, ?, ?, ?, ?, ?)\n"
+" DELETE_MESSAGE_REF=DELETE FROM JBM_MSG_REF WHERE MESSAGE_ID=? AND "
+"CHANNEL_ID=? AND STATE='C'\n"
+" UPDATE_MESSAGE_REF=UPDATE JBM_MSG_REF SET TRANSACTION_ID=?, STATE='-' "
+"WHERE MESSAGE_ID=? AND CHANNEL_ID=? AND STATE='C'\n"
+" UPDATE_PAGE_ORDER=UPDATE JBM_MSG_REF SET PAGE_ORD = ? WHERE MESSAGE_ID=? "
+"AND CHANNEL_ID=?\n"
+" COMMIT_MESSAGE_REF1=UPDATE JBM_MSG_REF SET STATE='C', TRANSACTION_ID = "
+"NULL WHERE TRANSACTION_ID=? AND STATE='+'\n"
+" COMMIT_MESSAGE_REF2=DELETE FROM JBM_MSG_REF WHERE TRANSACTION_ID=? AND "
+"STATE='-'\n"
+" ROLLBACK_MESSAGE_REF1=DELETE FROM JBM_MSG_REF WHERE TRANSACTION_ID=? AND "
+"STATE='+'\n"
+" ROLLBACK_MESSAGE_REF2=UPDATE JBM_MSG_REF SET STATE='C', TRANSACTION_ID = "
+"NULL WHERE TRANSACTION_ID=? AND STATE='-'\n"
+" LOAD_PAGED_REFS=SELECT MESSAGE_ID, DELIVERY_COUNT, PAGE_ORD, "
+"SCHED_DELIVERY FROM JBM_MSG_REF WHERE CHANNEL_ID = ? AND PAGE_ORD BETWEEN ? "
+"AND ? ORDER BY PAGE_ORD\n"
+" LOAD_UNPAGED_REFS=SELECT MESSAGE_ID, DELIVERY_COUNT, SCHED_DELIVERY FROM "
+"JBM_MSG_REF WHERE STATE = 'C' AND CHANNEL_ID = ? AND PAGE_ORD IS NULL ORDER "
+"BY ORD\n"
+" LOAD_REFS=SELECT MESSAGE_ID, DELIVERY_COUNT, SCHED_DELIVERY FROM "
+"JBM_MSG_REF WHERE STATE = 'C' AND CHANNEL_ID = ? ORDER BY ORD \n"
+" UPDATE_REFS_NOT_PAGED=UPDATE JBM_MSG_REF SET PAGE_ORD = NULL WHERE "
+"PAGE_ORD BETWEEN ? AND ? AND CHANNEL_ID=?\n"
+" SELECT_MIN_MAX_PAGE_ORD=SELECT MIN(PAGE_ORD), MAX(PAGE_ORD) FROM "
+"JBM_MSG_REF WHERE CHANNEL_ID = ?\n"
+" SELECT_EXISTS_REF_MESSAGE_ID=SELECT MESSAGE_ID FROM JBM_MSG_REF WHERE "
+"MESSAGE_ID = ?\n"
+" UPDATE_DELIVERY_COUNT=UPDATE JBM_MSG_REF SET DELIVERY_COUNT = ? WHERE "
+"CHANNEL_ID = ? AND MESSAGE_ID = ?\n"
+" UPDATE_CHANNEL_ID=UPDATE JBM_MSG_REF SET CHANNEL_ID = ? WHERE CHANNEL_ID "
+"= ?\n"
+" LOAD_MESSAGES=SELECT MESSAGE_ID, RELIABLE, EXPIRATION, TIMESTAMP, "
+"PRIORITY, HEADERS, PAYLOAD, TYPE FROM JBM_MSG\n"
+" INSERT_MESSAGE=INSERT INTO JBM_MSG (MESSAGE_ID, RELIABLE, EXPIRATION, "
+"TIMESTAMP, PRIORITY, TYPE, HEADERS, PAYLOAD) VALUES "
+"(?, ?, ?, ?, ?, ?, ?, ?)\n"
+" INSERT_MESSAGE_CONDITIONAL=INSERT INTO JBM_MSG (MESSAGE_ID, RELIABLE, "
+"EXPIRATION, TIMESTAMP, PRIORITY, TYPE, INST_TIME) SELECT ?, ?, ?, ?, ?, ?, ? "
+"FROM JBM_DUAL WHERE NOT EXISTS (SELECT MESSAGE_ID FROM JBM_MSG WHERE "
+"MESSAGE_ID = ?)\n"
+" UPDATE_MESSAGE_4CONDITIONAL=UPDATE JBM_MSG SET HEADERS=?, PAYLOAD=? WHERE "
+"MESSAGE_ID=?\n"
+" INSERT_MESSAGE_CONDITIONAL_FULL=INSERT INTO JBM_MSG (MESSAGE_ID, "
+"RELIABLE, EXPIRATION, TIMESTAMP, PRIORITY, TYPE, HEADERS, PAYLOAD) "
+"SELECT ?, ?, ?, ?, ?, ?, ?, ? FROM JBM_DUAL WHERE NOT EXISTS (SELECT "
+"MESSAGE_ID FROM JBM_MSG WHERE MESSAGE_ID = ?) \n"
+" MESSAGE_ID_COLUMN=MESSAGE_ID \n"
+" DELETE_MESSAGE=DELETE FROM JBM_MSG WHERE MESSAGE_ID = ? AND NOT EXISTS "
+"(SELECT * FROM JBM_MSG_REF WHERE JBM_MSG_REF.MESSAGE_ID = ?) \n"
+" INSERT_TRANSACTION=INSERT INTO JBM_TX (NODE_ID, TRANSACTION_ID, "
+"BRANCH_QUAL, FORMAT_ID, GLOBAL_TXID) VALUES(?, ?, ?, ?, ?)\n"
+" DELETE_TRANSACTION=DELETE FROM JBM_TX WHERE NODE_ID = ? AND "
+"TRANSACTION_ID = ?\n"
+" SELECT_PREPARED_TRANSACTIONS=SELECT TRANSACTION_ID, BRANCH_QUAL, "
+"FORMAT_ID, GLOBAL_TXID FROM JBM_TX WHERE NODE_ID = ?\n"
+" SELECT_MESSAGE_ID_FOR_REF=SELECT MESSAGE_ID, CHANNEL_ID FROM JBM_MSG_REF "
+"WHERE TRANSACTION_ID = ? AND STATE = '+' ORDER BY ORD\n"
+" SELECT_MESSAGE_ID_FOR_ACK=SELECT MESSAGE_ID, CHANNEL_ID FROM JBM_MSG_REF "
+"WHERE TRANSACTION_ID = ? AND STATE = '-' ORDER BY ORD\n"
+" UPDATE_COUNTER=UPDATE JBM_COUNTER SET NEXT_ID = ? WHERE NAME=?\n"
+" SELECT_COUNTER=SELECT NEXT_ID FROM JBM_COUNTER WHERE NAME=? FOR UPDATE\n"
+" INSERT_COUNTER=INSERT INTO JBM_COUNTER (NAME, NEXT_ID) VALUES (?, ?)\n"
+" SELECT_ALL_CHANNELS=SELECT DISTINCT(CHANNEL_ID) FROM JBM_MSG_REF\n"
+" UPDATE_TX=UPDATE JBM_TX SET NODE_ID=? WHERE NODE_ID=?\n"
+" ]]></attribute>\n"
+" \n"
+" <!-- The maximum number of parameters to include in a prepared "
+"statement -->\n"
+" \n"
+" <attribute name=\"MaxParams\">500</attribute>\n"
+"\n"
+" <attribute name=\"UseNDBFailoverStrategy\">true</"
+"attribute>\n"
+" \n"
+" </mbean>"
#. Tag: title
#: Configuration.xml:617
#, no-c-format
msgid "MBean attributes of the PersistenceManager MBean"
-msgstr ""
+msgstr "PersistenceManager MBean 的 MBean 属性"
#. Tag: para
#: Configuration.xml:621
@@ -2031,13 +2175,13 @@
"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 "如果你希望 Persistence Manager 在启动时创建表（以及索引），请将其设置为 <literal>true</literal>。如果这些表（以及索引）已经存在，JDBC 驱动将抛出一个 <literal>SQLException</literal>，Persistence Manager 会忽略这个异常并继续运行。"
#. Tag: title
#: Configuration.xml:632 Configuration.xml:723
#, no-c-format
msgid "UsingBatchUpdates"
-msgstr ""
+msgstr "UsingBatchUpdates"
#. Tag: para
#: Configuration.xml:633 Configuration.xml:724
@@ -2046,7 +2190,7 @@
"Set this to <literal>true</literal> if the database supports JDBC batch "
"updates. The JDBC Persistence Manager will then group multiple database "
"updates in batches to aid performance."
-msgstr ""
+msgstr "如果数据库支持 JDBC 批量更新，请设置它为 <literal>true</literal>。JDBC Persistence Manager 将对批量的数据库更新进行分组来提供性能。"
#. Tag: para
#: Configuration.xml:636 Configuration.xml:727
@@ -2054,13 +2198,13 @@
msgid ""
"By default the value of <literal>UsingBatchUpdates</literal> attribute is "
"set to <literal>false</literal>"
-msgstr ""
+msgstr "<literal>UsingBatchUpdates</literal> 属性的缺省值是 <literal>false</literal>。"
#. Tag: title
#: Configuration.xml:640
#, no-c-format
msgid "UsingBinaryStream"
-msgstr ""
+msgstr "UsingBinaryStream"
#. Tag: para
#: Configuration.xml:641
@@ -2070,7 +2214,7 @@
"read using a JDBC binary stream rather than using getBytes(), setBytes(). "
"Some database has limits on the maximum number of bytes that can be get/set "
"using getBytes()/setBytes()."
-msgstr ""
+msgstr "如果你希望用 JDBC 二进制流而不是 getBytes()、setBytes() 存储和读取消息，请设置它为 <literal>true</literal>。有些数据库对用 getBytes()/setBytes() 读取/写的字节数有限制。"
#. Tag: para
#: Configuration.xml:646
@@ -2078,17 +2222,18 @@
msgid ""
"By default the value of <literal>UsingBinaryStream</literal> attribute is "
"set to <literal>true</literal>"
-msgstr ""
+msgstr "<literal>UsingBinaryStream</literal> 属性的缺省值是 <literal>true</literal>。"
#. Tag: title
#: Configuration.xml:650
#, no-c-format
msgid "UsingTrailingByte"
-msgstr ""
+msgstr "UsingTrailingByte"
#. Tag: para
#: Configuration.xml:651
#, no-c-format
+#, fuzzy
msgid ""
"Certain version of Sybase are known to truncate blobs if they have trailing "
"zeros. To prevent this if this attribute is set to <literal>true</literal> "
@@ -2096,6 +2241,8 @@
"and after persistence to prevent the database from truncating it. Currently "
"this is only known to be necessary for Sybase."
msgstr ""
+"Sybase 的某些版本 "
+"目前这仅对于 Sybase 是必需的。"
#. Tag: para
#: Configuration.xml:657
@@ -2103,13 +2250,13 @@
msgid ""
"By default the value of <literal>UsingTrailingByte</literal> attribute is "
"set to <literal>false</literal>"
-msgstr ""
+msgstr "<literal>UsingTrailingByte</literal> 属性的缺省值是 <literal>false</literal>。"
#. Tag: title
#: Configuration.xml:661
#, no-c-format
msgid "SupportsBlobOnSelect"
-msgstr ""
+msgstr "SupportsBlobOnSelect"
#. Tag: para
#: Configuration.xml:662
@@ -2119,7 +2266,7 @@
"inserted using a INSERT INTO ... SELECT FROM statement, and requires a two "
"stage conditional insert of messages. If this value is false then such a two "
"stage insert will be used."
-msgstr ""
+msgstr "Oracle（可能还有其他数据库）不允许用 INSERT INTO ... SELECT FROM 语句插入 BLOB，且要求两阶段插入消息。如果这个值为 false，那么将使用两阶段的插入。"
#. Tag: para
#: Configuration.xml:667
@@ -2127,13 +2274,13 @@
msgid ""
"By default the value of <literal>SupportsBlobOnSelect</literal> attribute is "
"set to <literal>true</literal>"
-msgstr ""
+msgstr "<literal>SupportsBlobOnSelect</literal> 属性缺省值是 <literal>true</literal>。"
#. Tag: title
#: Configuration.xml:679
#, no-c-format
msgid "MaxParams"
-msgstr ""
+msgstr "MaxParams"
#. Tag: para
#: Configuration.xml:680
@@ -2143,7 +2290,7 @@
"statements with many parameters. This value tells the persistence manager "
"what the absolute maximum number of parameters are allowable per prepared "
"statement."
-msgstr ""
+msgstr "当加载消息时，Persistence manager 将生成带有很多参数的 prepared 语句。这个值通知 Persistence manager 每个 prepared 语句所允许的参数的最大个数。"
#. Tag: para
#: Configuration.xml:684
@@ -2151,7 +2298,7 @@
msgid ""
"By default the value of <literal>MaxParams</literal> attribute is set to "
"<literal>100</literal>"
-msgstr ""
+msgstr "<literal>MaxParams</literal> 属性的缺省值是<literal>100</literal>。"
#. Tag: title
#: Configuration.xml:688
More information about the jboss-cvs-commits
mailing list