[jboss-svn-commits] JBL Code SVN: r34738 - labs/jbossesb/branches/JBESB_4_9_CP/product/docs/Services_Guide/en-US.

[jboss-svn-commits at lists.jboss.org]

Author: dlesage
Date: 2010-08-16 00:20:54 -0400 (Mon, 16 Aug 2010)
New Revision: 34738

Modified:
   labs/jbossesb/branches/JBESB_4_9_CP/product/docs/Services_Guide/en-US/content-based_routing_using_regex.xml
Log:
JBESB 3460

Modified: labs/jbossesb/branches/JBESB_4_9_CP/product/docs/Services_Guide/en-US/content-based_routing_using_regex.xml
===================================================================
--- labs/jbossesb/branches/JBESB_4_9_CP/product/docs/Services_Guide/en-US/content-based_routing_using_regex.xml	2010-08-16 03:58:23 UTC (rev 34737)
+++ labs/jbossesb/branches/JBESB_4_9_CP/product/docs/Services_Guide/en-US/content-based_routing_using_regex.xml	2010-08-16 04:20:54 UTC (rev 34738)
@@ -19,8 +19,8 @@
 	<para>
     	An easy way to perform content-based routing in JBoss Enterprise
     	Service Bus is via the <firstterm>Regex rules provider</firstterm>
-    	on the <classname>ContentBasedRouter</classname> action. One will
-    	find this provider very easy to use and it supports both inline and
+    	on the <classname>ContentBasedRouter</classname> action. This
+        provider is very easy to use and it supports both inline and
     	external rule definitions.
     </para>
 </section>    
@@ -31,18 +31,27 @@
         Inline Rule Definitions
     </title>
     
-    <para>
-        Defining inline Regex routing rules is very straightforward. One
-        merely needs to set the <property>cbrAlias</property> property to
-        <code>Regex</code> and then define the routing rules in the
-        <property>route-to</property> configurations, found in the
-        <property>container destinations</property> property. 
-    </para>
-    
 
-         <programlisting language="XML" role="XML"><xi:include href="extras/cbr_regex/regex.xmlt" parse="text" xmlns:xi="http://www.w3.org/2001/XInclude"></xi:include></programlisting>        
-	
+    <procedure>
+      <title>Defining Inline Regex Routing Rules</title>
+      <step>
+        <para> set the <property>cbrAlias</property> property to
+        <code>Regex</code></para>
 
+      </step>
+<step>
+<para>
+  define the routing rules in the
+  <property>route-to</property> configurations, found in the
+  <property>container destinations</property> property. 
+</para>
+
+
+<programlisting language="XML" role="XML"><xi:include href="extras/cbr_regex/regex.xmlt" parse="text" xmlns:xi="http://www.w3.org/2001/XInclude"></xi:include></programlisting>    
+</step>
+    </procedure>	
+
+
 </section>
 
 <section>
@@ -50,22 +59,25 @@
         External Rule Definitions
 </title>
 
-<para>
-    Defining external XPath routing rules is also quite simple. Again, one
-    merely needs to set the <property>cbrAlias</property> property to
-    <code>Regex</code> and then:
-</para>
 
-<orderedlist>
-<listitem>
-<para>
+
+<procedure><title>Setting External Rule Definitions</title>
+<step>
+  <para> set the <property>cbrAlias</property> property to
+  <code>Regex</code></para>
+
+</step>
+<step>
+  <para>
     define the routing expressions in a <filename>.properties</filename>
     file, where the property keys are the destination names and the property
     values are the Regex expressions for routing to the destination in
     question.
-</para>
-</listitem>
-<listitem>
+  </para>
+</step>
+
+
+<step>
 <para>
     define the routing rules in the <code>route-to</code> configurations in the
     container destinations property, with the
@@ -73,24 +85,20 @@
     Regex rule key as defined in the external
     <filename>.properties</filename> file.
 </para>
-</listitem>
-</orderedlist>
 
-
-         <programlisting language="XML" role="XML"><xi:include href="extras/cbr_regex/external2.xmlt" parse="text" xmlns:xi="http://www.w3.org/2001/XInclude"></xi:include></programlisting>        
-
-
-
+<programlisting language="XML" role="XML"><xi:include href="extras/cbr_regex/external2.xmlt" parse="text" xmlns:xi="http://www.w3.org/2001/XInclude"></xi:include></programlisting>    
 <para>
-    The XPath rules are in a <filename>.properties</filename> file. They are
-    represented in this simple format:
+  The XPath rules are in a <filename>.properties</filename> file. They are
+  represented in this simple format:
 </para>
 
 
-         <programlisting language="XML" role="XML"><xi:include href="extras/cbr_regex/xpathrules2.xmlt" parse="text" xmlns:xi="http://www.w3.org/2001/XInclude"></xi:include></programlisting>        
+<programlisting language="XML" role="XML"><xi:include href="extras/cbr_regex/xpathrules2.xmlt" parse="text" xmlns:xi="http://www.w3.org/2001/XInclude"></xi:include></programlisting>        
 
+</step>
+</procedure>
 
-
+        
 </section>