svn commit: r911715 - /synapse/trunk/java/src/site/xdoc/Synapse_Configuration_Language.xml

[hi...@apache.org]

Author: hiranya
Date: Fri Feb 19 06:31:57 2010
New Revision: 911715

URL: http://svn.apache.org/viewvc?rev=911715&view=rev
Log:
Documentation update for SYNAPSE-610



Modified:
    synapse/trunk/java/src/site/xdoc/Synapse_Configuration_Language.xml

Modified: synapse/trunk/java/src/site/xdoc/Synapse_Configuration_Language.xml
URL: http://svn.apache.org/viewvc/synapse/trunk/java/src/site/xdoc/Synapse_Configuration_Language.xml?rev=911715&r1=911714&r2=911715&view=diff
==============================================================================
--- synapse/trunk/java/src/site/xdoc/Synapse_Configuration_Language.xml (original)
+++ synapse/trunk/java/src/site/xdoc/Synapse_Configuration_Language.xml Fri Feb 19 06:31:57 2010
@@ -760,7 +760,7 @@
     <p>
       A &lt;proxy&gt; element is used to define a Synapse Proxy service.
     </p>
-<pre xml:space="preserve"> &lt;proxy name="string" [transports="(http |https |jms |.. )+|all"] [pinnedServers="(serverName )+"]&gt;
+<pre xml:space="preserve"> &lt;proxy name="string" [transports="(http |https |jms |.. )+|all"] [pinnedServers="(serverName )+"] [serviceGroup="string"]&gt;
    &lt;description&gt;...&lt;/description&gt;?
    &lt;target [inSequence="name"] [outSequence="name"] [faultSequence="name"] [endpoint="name"]&gt;
       &lt;inSequence&gt;...&lt;/inSequence&gt;?
@@ -801,6 +801,14 @@
       or by editing the wrapper.conf where Synapse is started as a service.
     </p>
     <p>
+      By default when a proxy service is created it is added to an Axis service
+      group which has the same name as the proxy service. With the 'serviceGroup'
+      attribute this behavior can be further configured. A custom Axis service
+      group can be specified for a proxy service using the 'serviceGroup' attribute.
+      This way multiple proxy services can be grouped together at Axis2 level
+      thus greeatly simplifying service management tasks.
+    </p>
+    <p>
       Each service could define the target for received messages as a named
       sequence or a direct endpoint. Target inSequence or endpoint is required
       for the proxy configuration, and a target outSequence defines how