[hornetq-commits] JBoss hornetq SVN: r9015 - branches/HnetQ_323_cn/docs/user-manual/zh.

do-not-reply at jboss.org do-not-reply at jboss.org
Tue Mar 30 11:04:16 EDT 2010


Author: gaohoward
Date: 2010-03-30 11:04:15 -0400 (Tue, 30 Mar 2010)
New Revision: 9015

Modified:
   branches/HnetQ_323_cn/docs/user-manual/zh/filter-expressions.xml
   branches/HnetQ_323_cn/docs/user-manual/zh/wildcard-routing.xml
   branches/HnetQ_323_cn/docs/user-manual/zh/wildcard-syntax.xml
Log:
another 3 chapters


Modified: branches/HnetQ_323_cn/docs/user-manual/zh/filter-expressions.xml
===================================================================
--- branches/HnetQ_323_cn/docs/user-manual/zh/filter-expressions.xml	2010-03-30 09:46:28 UTC (rev 9014)
+++ branches/HnetQ_323_cn/docs/user-manual/zh/filter-expressions.xml	2010-03-30 15:04:15 UTC (rev 9015)
@@ -19,64 +19,53 @@
 <!-- ============================================================================= -->
 
 <chapter id="filter-expressions">
-    <title>Filter Expressions</title>
-    <para>HornetQ provides a powerful filter language based on a subset of the SQL 92
-        expression syntax.</para>
-    <para>It is the same as the syntax used for JMS selectors, but the predefined identifiers are
-        different. For documentation on JMS selector syntax please the JMS javadoc for <ulink
+    <title>过滤器表达式</title>
+    <para>HornetQ提供了一套强大的过滤器(filter)语言。它的语法是基于SQL 92表达式的部分语法。</para>
+    <para>实际上它与JMS选择器(selector)的语法是相同的。只是其中有一些预定义的标识符有所不同。有关
+            JMS选择器的相关知识参见 <ulink
             url="http://java.sun.com/javaee/5/docs/api/javax/jms/Message.html"
-            >javax.jms.Message</ulink>.</para>
-    <para>Filter expressions are used in several places in HornetQ</para>
+            >javax.jms.Message</ulink>。</para>
+    <para>HornetQ在以下以个地方使用了过滤器表达式:</para>
     <itemizedlist>
         <listitem>
-            <para>Predefined Queues. When pre-defining a queue, either in <literal
-                    >hornetq-configuration.xml</literal> or <literal>hornetq-jms.xml</literal> a filter
-                expression can be defined for a queue. Only messages that match the filter
-                expression will enter the queue.</para>
+            <para>预定义的队列。当在<literal
+                    >hornetq-configuration.xml</literal> 或 <literal>hornetq-jms.xml</literal>定义
+                队列时,可以使用过滤器。只有与过滤器表达式相匹配的消息才能达到该队列中。</para>
         </listitem>
         <listitem>
-            <para>Core bridges can be defined with an optional filter expression, only matching
-                messages will be bridged (see <xref linkend="core-bridges"/>).</para>
+            <para>核心桥可以使用可选的过滤器表达式。只有与表达式相匹配的消息才被桥处理。
+                参见(<xref linkend="core-bridges"/>)。</para>
         </listitem>
         <listitem>
-            <para>Diverts can be defined with an optional filter expression, only matching messages
-                will be diverted (see <xref linkend="diverts" />).</para>
+            <para>转移(Divert)也可以使用可选的过滤器表达式。只有与表达式匹配的消息才被转移。
+                参见(<xref linkend="diverts" />)。</para>
         </listitem>
         <listitem>
-            <para>Filter are also used programmatically when creating consumers, queues and in
-                several places as described in <xref linkend="management"/>.</para>
+            <para>另外过滤器还可以在编程方式创建接收者(consumer)和队列时使用。还有一些应用过滤器的地方在
+               <xref linkend="management"/>中有所描述。</para>
         </listitem>
     </itemizedlist>
-    <para>There are some differences between JMS selector expressions and HornetQ core
-        filter expressions. Whereas JMS selector expressions operate on a JMS message, HornetQ
-        core filter expressions operate on a core message.</para>
-    <para>The following identifiers can be used in a core filter expressions to refer to attributes
-        of the core message in an expression:</para>
+    <para>HornetQ的内核过滤器表达式与JMS选择器表达式是有所不同的。JMS选择器应用于JMS消息,而HornetQ的内核过滤
+        器表达式则用于内核消息。</para>
+    <para>以下标识符可以用在内核消息的过滤器表达式中,用来引用内核消息的属性:</para>
     <itemizedlist>
         <listitem>
-            <para><literal>HQPriority</literal>. To refer to the priority of a message. Message
-                priorities are integers with valid values from <literal>0 - 9</literal>. <literal
-                    >0</literal> is the lowest priority and <literal>9</literal> is the highest.
-                E.g. <literal>HQPriority = 3 AND animal = 'aardvark'</literal></para>
+            <para><literal>HQPriority</literal>。代表消息的优先级。消息优先级属性的有效值为0到9间的整数。
+                 0为最低优先级,9为最高优先级。例:<literal>HQPriority = 3 AND animal = 'aardvark'</literal>。</para>
         </listitem>
         <listitem>
-            <para><literal>HQExpiration</literal>. To refer to the expiration time of a message.
-                The value is a long integer.</para>
+            <para><literal>HQExpiration</literal>。代表消息的失效时间。其值为一长整形数。</para>
         </listitem>
         <listitem>
-            <para><literal>HQDurable</literal>. To refer to whether a message is durable or not.
-                The value is a string with valid values: <literal>DURABLE</literal> or <literal
-                    >NON_DURABLE</literal>.</para>
+            <para><literal>HQDurable</literal>。代表消息是否是持久消息。它是一个字符型的属性,有效值为 <literal>DURABLE</literal> 
+                   或 <literal>NON_DURABLE</literal>。</para>
         </listitem>
         <listitem>
-            <para><literal>HQTimestamp</literal>. The timestamp of when the message was created.
-                The value is a long integer.</para>
+            <para><literal>HQTimestamp</literal>。代表消息的创建时间,其值为一长整形数。</para>
         </listitem>
         <listitem>
-            <para><literal>HQSize</literal>. The size of a message in bytes. The value is an
-                integer.</para>
+            <para><literal>HQSize</literal>。消息的大小。单位为字节。其值是一个整形数。</para>
         </listitem>
     </itemizedlist>
-    <para>Any other identifiers used in core filter expressions will be assumed to be properties of
-        the message.</para>
+    <para>任何其它的标识符在内核过滤器的表达式中都认为是代表着该消息的一个属性。</para>
 </chapter>

Modified: branches/HnetQ_323_cn/docs/user-manual/zh/wildcard-routing.xml
===================================================================
--- branches/HnetQ_323_cn/docs/user-manual/zh/wildcard-routing.xml	2010-03-30 09:46:28 UTC (rev 9014)
+++ branches/HnetQ_323_cn/docs/user-manual/zh/wildcard-routing.xml	2010-03-30 15:04:15 UTC (rev 9015)
@@ -19,21 +19,19 @@
 <!-- ============================================================================= -->
 
 <chapter id="wildcard-routing">
-    <title>Routing Messages With Wild Cards</title>
-    <para>HornetQ allows the routing of messages via wildcard addresses.</para>
-    <para>If a consumer is created with an address of say <literal>queue.news.#</literal> then it
-        will receive any messages sent to addresses that match this, for instance <literal
-            >queue.news.europe</literal> or <literal>queue.news.usa</literal> or <literal
-            >queue.news.usa.sport</literal>. This allows a consumer to consume messages which are
-        sent to a <emphasis>hierarchy</emphasis> of addresses, rather than the consumer having to
-        specify a specific address.</para>
+    <title>使用通配符实现消息路由</title>
+    <para>HornetQ支持使用带通配符的地址对消息路由。</para>
+    <para>例如,当创建一个接收者(consumer)时使用了地址<literal>queue.news.#</literal>,那么它就能接收
+          所有和这个地址通配符相配的每一个地址的消息。这样的地址如 <literal
+            >queue.news.europe</literal> 或 <literal>queue.news.usa</literal> 或 <literal
+            >queue.news.usa.sport</literal>等。这样一个消息接收者可以接收<literal>一组</literal>相关
+          的地址的消息,而不是只能指定一个具体的地址。</para>
     <note>
-        <para>In JMS terminology this allows "topic hierarchies" to be created.</para>
+        <para>用JMS的术语来说,这个功能就是允许创建“话题组”(topic hierarchy)。</para>
     </note>
-    <para>To enable this functionality set the property <literal>wild-card-routing-enabled</literal>
-        in the <literal>hornetq-configuration.xml</literal> file to <literal>true</literal>. This is
-            <literal>true</literal> by default.</para>
-    <para>For more information on the wild card syntax take a look at <xref
-            linkend="wildcard-syntax" /> chapter, also see <xref
-            linkend="topic-hierarchy-example" />.</para>
+    <para>要使用本功能需要将<literal>wild-card-routing-enabled</literal>属性设置为<literal>true</literal>。
+        这个属性在 <literal>hornetq-configuration.xml</literal> 文件中。默认值是<literal>true</literal>。</para>
+    <para>关于通配符的语法参见<xref
+            linkend="wildcard-syntax" /> 章及 <xref
+            linkend="topic-hierarchy-example" />。</para>
 </chapter>

Modified: branches/HnetQ_323_cn/docs/user-manual/zh/wildcard-syntax.xml
===================================================================
--- branches/HnetQ_323_cn/docs/user-manual/zh/wildcard-syntax.xml	2010-03-30 09:46:28 UTC (rev 9014)
+++ branches/HnetQ_323_cn/docs/user-manual/zh/wildcard-syntax.xml	2010-03-30 15:04:15 UTC (rev 9015)
@@ -19,21 +19,19 @@
 <!-- ============================================================================= -->
 
 <chapter id="wildcard-syntax">
-    <title>Understanding the HornetQ Wildcard Syntax</title>
-    <para>HornetQ uses a specific syntax for representing wildcards in security settings,
-        address settings and when creating consumers.</para>
-    <para>The syntax is similar to that used by <ulink url="www.amqp.org">AMQP</ulink>.</para>
-    <para>A HornetQ wildcard expression contains words delimited by the character '<literal
-            >.</literal>' (full stop).</para>
-    <para>The special characters '<literal>#</literal>' and '<literal>*</literal>' also have special
-        meaning and can take the place of a word.</para>
-    <para>The character '<literal>#</literal>' means 'match any sequence of zero or more
-        words'.</para>
-    <para>The character '<literal>*</literal>' means 'match a single word'.</para>
-    <para>So the wildcard 'news.europe.#' would match 'news.europe', 'news.europe.sport',
-        'news.europe.politics', and 'news.europe.politics.regional' but would not match 'news.usa',
-        'news.usa.sport' nor 'entertainment'.</para>
-    <para>The wildcard 'news.*' would match 'news.europe', but not 'news.europe.sport'.</para>
-    <para>The wildcard 'news.*.sport' would match 'news.europe.sport' and also 'news.usa.sport', but
-        not 'news.europe.politics'.</para>
+    <title>了解 HornetQ 通配符的语法</title>
+    <para>HornetQ使用了一种专门的通配符语法来配置安全、地址及接收者(consumer)的创建。</para>
+    <para>这种语法与 <ulink url="www.amqp.org">AMQP</ulink>所用的语法相似。</para>
+    <para>一个HornetQ的通配符表达式是由一些由“<literal
+            >.</literal>”分隔的单词组成。</para>
+    <para>特殊字符“<literal>#</literal>”和“<literal>*</literal>”在表达式中可作为一个单词,它们代表
+        特殊的意义。</para>
+    <para>字符“<literal>#</literal>”表示“零或多个单词的任意排列”。</para>
+    <para>字符“<literal>*</literal>”表示“一个单词”。</para>
+    <para>因此,通配符表达式“news.europe.#”可以匹配“news.europe”、“news.europe.sport”、
+        “news.europe.politics”以及“news.europe.politics.regional”,但是与“news.usa”、
+        “news.usa.sport” 及 “entertainment”不相匹配。</para>
+    <para>通配符“news.*”与“news.europe”匹配,但不与“news.europe.sport”匹配。</para>
+    <para>通配符“news.*.sport”与“news.europe.sport”及“news.usa.sport”匹配,但与
+        “news.europe.politics”不匹配。</para>
 </chapter>



More information about the hornetq-commits mailing list