You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@synapse.apache.org by hi...@apache.org on 2010/02/19 07:31:03 UTC
svn commit: r911714 -
/synapse/branches/1.3/src/site/xdoc/Synapse_Configuration_Language.xml
Author: hiranya
Date: Fri Feb 19 06:31:03 2010
New Revision: 911714
URL: http://svn.apache.org/viewvc?rev=911714&view=rev
Log:
Documentation update for SYNAPSE-610
Modified:
synapse/branches/1.3/src/site/xdoc/Synapse_Configuration_Language.xml
Modified: synapse/branches/1.3/src/site/xdoc/Synapse_Configuration_Language.xml
URL: http://svn.apache.org/viewvc/synapse/branches/1.3/src/site/xdoc/Synapse_Configuration_Language.xml?rev=911714&r1=911713&r2=911714&view=diff
==============================================================================
--- synapse/branches/1.3/src/site/xdoc/Synapse_Configuration_Language.xml (original)
+++ synapse/branches/1.3/src/site/xdoc/Synapse_Configuration_Language.xml Fri Feb 19 06:31:03 2010
@@ -760,7 +760,7 @@
<p>
A <proxy> element is used to define a Synapse Proxy service.
</p>
-<pre xml:space="preserve"> <proxy name="string" [transports="(http |https |jms |.. )+|all"] [pinnedServers="(serverName )+"]>
+<pre xml:space="preserve"> <proxy name="string" [transports="(http |https |jms |.. )+|all"] [pinnedServers="(serverName )+"] [serviceGroup="string"]>
<description>...</description>?
<target [inSequence="name"] [outSequence="name"] [faultSequence="name"] [endpoint="name"]>
<inSequence>...</inSequence>?
@@ -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