INT-1516 added docs for RLR's selector-expression, fixed the docbook error'

docs/src/reference/docbook/control-bus.xml

@@ -1,10 +1,6 @@
 <?xml version="1.0" encoding="UTF-8"?>
-<section version="5.0" xml:id="jmx" xmlns="http://docbook.org/ns/docbook"
-         xmlns:xlink="http://www.w3.org/1999/xlink"
-         xmlns:ns5="http://www.w3.org/1999/xhtml"
-         xmlns:ns4="http://www.w3.org/1998/Math/MathML"
-         xmlns:ns3="http://www.w3.org/2000/svg"
-         xmlns:ns="http://docbook.org/ns/docbook">
+<section xmlns="http://docbook.org/ns/docbook" version="5.0" xml:id="control-bus"
+    xmlns:xlink="http://www.w3.org/1999/xlink">
   <title>Control Bus</title>
 
   <para>As described in (EIP), the idea behind the Control Bus is that
@@ -12,10 +8,11 @@
   the components within the framework as is used for
   "application-level" messaging. In Spring Integration we build upon
   the adapters described above so that it's possible to send Messages
-  as a means of invoking exposed operations.</para>
+  as a means of invoking exposed operations.
+  
+  <programlisting language="xml"><![CDATA[<int:control-bus input-channel="operationChannel"/>]]></programlisting>
 
-  <programlisting language="xml"><![CDATA[
-<groovy:control-bus input-channel="operationChannel"/></programlisting>
+  </para>
 
   <para>The Control Bus has an input channel that can be accessed for
   invoking operations on the beans in the application context.  It

docs/src/reference/docbook/jmx.xml

@@ -1,10 +1,6 @@
 <?xml version="1.0" encoding="UTF-8"?>
-<section version="5.0" xml:id="jmx" xmlns="http://docbook.org/ns/docbook"
-         xmlns:xlink="http://www.w3.org/1999/xlink"
-         xmlns:ns5="http://www.w3.org/1999/xhtml"
-         xmlns:ns4="http://www.w3.org/1998/Math/MathML"
-         xmlns:ns3="http://www.w3.org/2000/svg"
-         xmlns:ns="http://docbook.org/ns/docbook">
+<section xmlns="http://docbook.org/ns/docbook" version="5.0" xml:id="jmx"
+    xmlns:xlink="http://www.w3.org/1999/xlink">
   <title>JMX Support</title>
 
   <para>Spring Integration provides Channel Adapters for receiving and

docs/src/reference/docbook/router.xml

@@ -128,11 +128,25 @@
   <recipient channel="channel2"/>
 </recipient-list-router>]]></programlisting>
   </para>
-    <note>
+  <note>
       The 'apply-sequence' flag here has the same affect as it does for a publish-subscribe-channel,
       and like publish-subscribe-channel it is disabled by default on the recipient-list-router. Refer to
       <xref linkend="channel-configuration-pubsubchannel"/> for more information.
   </note>
+  
+  <para>
+  Another convenient option to configure Recipient List Router is to use Spring Expression Language (SpEL) support
+  
+  <programlisting language="xml"><![CDATA[<int:recipient-list-router id="customRouter" input-channel="routingChannel">
+	<int:recipient channel="channel1" selector-expression="payload.equals('foo')"/>
+	<int:recipient channel="channel2" selector-expression="headers.contains('bar')"/>
+</int:recipient-list-router>]]></programlisting>
+
+	In the above configuration a SpEL expression identified by <code>selector-expression</code> attribute will be evaluated to determine if this recipient 
+ 	should be included in the recipient list for a given input Message. The evaluation result of the expression must be a boolean. If this 
+ 	attribute is not defined, the channel will always be among the list of recipients.
+  </para>
+    
   </section>
 
   <section id="router-namespace">

docs/src/reference/docbook/system-management.xml

@@ -3,9 +3,8 @@
     xmlns:xi="http://www.w3.org/2001/XInclude"
     xmlns:xlink="http://www.w3.org/1999/xlink">
   <title>System Management</title>
-
-	<xi:include href="./message-history.xml"/>
-    <xi:include href="./control-bus.xml"/>	
-    <xi:include href="./jmx.xml"/>	
-
-</chapter>
+  
+  <xi:include href="./control-bus.xml"/>
+  <xi:include href="./jmx.xml"/>
+  <xi:include href="./message-history.xml"/>
+</chapter>