[jboss-svn-commits] JBL Code SVN: r34735 - labs/jbossesb/branches/JBESB_4_9_CP/product/docs/Services_Guide/en-US.
jboss-svn-commits at lists.jboss.org
jboss-svn-commits at lists.jboss.org
Sun Aug 15 19:50:42 EDT 2010
Author: dlesage
Date: 2010-08-15 19:50:41 -0400 (Sun, 15 Aug 2010)
New Revision: 34735
Modified:
labs/jbossesb/branches/JBESB_4_9_CP/product/docs/Services_Guide/en-US/Registry_Troubleshooting.xml
labs/jbossesb/branches/JBESB_4_9_CP/product/docs/Services_Guide/en-US/Service_Orchestration.xml
labs/jbossesb/branches/JBESB_4_9_CP/product/docs/Services_Guide/en-US/content-based_routing_using_xpath.xml
Log:
JBESB 3460
Modified: labs/jbossesb/branches/JBESB_4_9_CP/product/docs/Services_Guide/en-US/Registry_Troubleshooting.xml
===================================================================
--- labs/jbossesb/branches/JBESB_4_9_CP/product/docs/Services_Guide/en-US/Registry_Troubleshooting.xml 2010-08-15 23:45:00 UTC (rev 34734)
+++ labs/jbossesb/branches/JBESB_4_9_CP/product/docs/Services_Guide/en-US/Registry_Troubleshooting.xml 2010-08-15 23:50:41 UTC (rev 34735)
@@ -21,7 +21,7 @@
<listitem>
<para>
- If using RMI, be sure to obtain the
+ If using remote method invocation, be sure to obtain the
<filename>juddi-client.jar</filename>, (found in the
<application>jUDDI</application> distribution.)
</para>
Modified: labs/jbossesb/branches/JBESB_4_9_CP/product/docs/Services_Guide/en-US/Service_Orchestration.xml
===================================================================
--- labs/jbossesb/branches/JBESB_4_9_CP/product/docs/Services_Guide/en-US/Service_Orchestration.xml 2010-08-15 23:45:00 UTC (rev 34734)
+++ labs/jbossesb/branches/JBESB_4_9_CP/product/docs/Services_Guide/en-US/Service_Orchestration.xml 2010-08-15 23:50:41 UTC (rev 34735)
@@ -166,12 +166,14 @@
</figure>
<para>
- After creating a new process definition. You can drag and drop
- any item from menu, shown in Figure 8, into the process design
- view. You can switch between the design and source modes if
- needed to check the XML elements that are being added, or to
- add XML fragments that are needed for the integration. Recently
- a new type of node was added called “ESB Service" [KA-BLOG].
+ After creating a new process definition, start to
+ "drag-and-drop" items from the <application>jBPM Integrated
+ Development Environment</application>'s menu palette into the
+ <guilabel>Process Design</guilabel> view. One can switch between
+ the design and source modes if need be, in order to check the
+ XML elements being added, or in order to add those XML fragments
+ that are needed for the integration. (Recently, a new type of
+ node called <firstterm>ESB Service</firstterm> was added.)
</para>
@@ -538,8 +540,7 @@
whilst existing ones will finish using the process deployment on
which they were started.
</para>
-</note>
-
+</note>
</section>
<section>
Modified: labs/jbossesb/branches/JBESB_4_9_CP/product/docs/Services_Guide/en-US/content-based_routing_using_xpath.xml
===================================================================
--- labs/jbossesb/branches/JBESB_4_9_CP/product/docs/Services_Guide/en-US/content-based_routing_using_xpath.xml 2010-08-15 23:45:00 UTC (rev 34734)
+++ labs/jbossesb/branches/JBESB_4_9_CP/product/docs/Services_Guide/en-US/content-based_routing_using_xpath.xml 2010-08-15 23:50:41 UTC (rev 34735)
@@ -17,14 +17,14 @@
<para>
- An easy way of performing content based routing in the JBoss Enterprise
- Service Bus is via the <firstterm>XPath Rules Provider</firstterm> on
+ An easy way to perform content-based routing
+ is by using the <firstterm>XPath Rules Provider</firstterm> on
the <classname>ContentBasedRouter</classname> action.
</para>
<para>
- This provider is very easy to use and supports both inline and external
- rule definitions.
+ This provider is very easy to use and supports both <firstterm>inline</firstterm> and <firstterm>external
+ rule definitions</firstterm>.
</para>
</section>
@@ -34,18 +34,25 @@
Inline Rule Definitions
</title>
-<para>
- It is very simple to define inline routing rules using XPath. One merely
- needs to set the <property>cbrAlias</property> property to
- <code>XPath</code> and then define the routing rules in the
- <code>route-to</code> configurations that are found in the container
- destinations property.
-</para>
- <programlisting language="XML" role="XML"><xi:include href="extras/cbr_xpath/xpathexample1.xmlt" parse="text" xmlns:xi="http://www.w3.org/2001/XInclude"></xi:include></programlisting>
+<procedure>
+ <title>Defining Inline Rules</title>
+ <step>
+ <para>Set the <property>cbrAlias</property> property to
+ <code>XPath</code></para>
+ </step>
+<step>
+ <para>Define the routing rules in the
+ <code>route-to</code> configurations (found in the <property>container
+ destinations property</property>):</para>
+ <programlisting language="XML" role="XML"><xi:include href="extras/cbr_xpath/xpathexample1.xmlt" parse="text" xmlns:xi="http://www.w3.org/2001/XInclude"></xi:include></programlisting>
+ </step>
+</procedure>
+
+
</section>
<section>
@@ -53,33 +60,29 @@
External Rule Definitions
</title>
- <para>
- It is also very straightforward to define external XPath routing
- rules. Again, one must set the <property>cbrAlias</property>
- property to <code>XPath</code> and then:
- </para>
-
-
-<orderedlist>
-<listitem>
-<para>
-define the routing expressions in a .properties file, in which the property
-keys are equal to the destination names and the property values are the XPath
-expressions for routing to the destination in question.
-</para>
-</listitem>
-<listitem>
-<para>
-define the routing rules in the <code>route-to</code> configurations via the container
-destinations property, whereby the <property>destination-name</property> attribute will refer to
-the XPath rule key as defined in the external .properties file.
-</para>
-</listitem>
-</orderedlist>
+ <procedure>
+ <title>Defining External Rules</title>
+ <step>
+ <para>Set the <property>cbrAlias</property> property to
+ <code>XPath</code></para>
+ </step>
+ <step>
+ <para>Define the routing expressions in a .properties file, in which the property
+ keys are equal to the destination names and the property values are the XPath
+ expressions for routing to the destination in question.</para>
+
+ </step>
- <programlisting language="XML" role="XML"><xi:include href="extras/cbr_xpath/xpathexample2.xmlt" parse="text" xmlns:xi="http://www.w3.org/2001/XInclude"></xi:include></programlisting>
+ <step>
+ <para>Define the routing rules in the <code>route-to</code> configurations via the container
+ destinations property, whereby the <property>destination-name</property> attribute will refer to
+ the XPath rule key as defined in the external .properties file.</para>
+
+ <programlisting language="XML" role="XML"><xi:include href="extras/cbr_xpath/xpathexample2.xmlt" parse="text" xmlns:xi="http://www.w3.org/2001/XInclude"></xi:include></programlisting>
+ </step>
+ </procedure>
<para>
@@ -99,18 +102,21 @@
</title>
<para>
- <abbrev>XML</abbrev> name-space prefix-to-URI mappings are defined
- in the <property>namespace</property> elements. These are contained
- within the <literal>namespaces</literal> container property. Name-space
- prefix-to-URI mappings are defined in exactly the same way for both
- inline and external rule definitions.
+ XML name-space prefix-to-URI mappings are defined
+ in the <property>namespace</property> elements. (These are contained
+ within the <property>namespaces</property> container
+ property.)
</para>
-
-
+ <procedure>
+ <title>Defining XML Name-space Prefix-to-URI Mappings</title>
+ <step>
+ <para>Define these in the same way for both external and
+ inline rule definitions:</para>
+ <programlisting language="XML" role="XML"><xi:include href="extras/cbr_xpath/namespaces.xmlt" parse="text" xmlns:xi="http://www.w3.org/2001/XInclude"></xi:include></programlisting>
+
+ </step>
+ </procedure>
- <programlisting language="XML" role="XML"><xi:include href="extras/cbr_xpath/namespaces.xmlt" parse="text" xmlns:xi="http://www.w3.org/2001/XInclude"></xi:include></programlisting>
-
-
</section>
</section>
More information about the jboss-svn-commits
mailing list