You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@synapse.apache.org by ru...@apache.org on 2010/12/03 07:07:44 UTC
svn commit: r1041705 -
/synapse/branches/2.0/src/site/xdoc/Synapse_Configuration_Language.xml
Author: ruwan
Date: Fri Dec 3 06:07:44 2010
New Revision: 1041705
URL: http://svn.apache.org/viewvc?rev=1041705&view=rev
Log:
Referring to the schema from the configuration language
Modified:
synapse/branches/2.0/src/site/xdoc/Synapse_Configuration_Language.xml
Modified: synapse/branches/2.0/src/site/xdoc/Synapse_Configuration_Language.xml
URL: http://svn.apache.org/viewvc/synapse/branches/2.0/src/site/xdoc/Synapse_Configuration_Language.xml?rev=1041705&r1=1041704&r2=1041705&view=diff
==============================================================================
--- synapse/branches/2.0/src/site/xdoc/Synapse_Configuration_Language.xml (original)
+++ synapse/branches/2.0/src/site/xdoc/Synapse_Configuration_Language.xml Fri Dec 3 06:07:44 2010
@@ -82,12 +82,14 @@
As the diagram below depicts, the Synapse configuration defines the Proxy
services, Endpoints, Sequences, Startup jobs, Event sources, Priority
executors and Dead letter channels managed by the Synapse ESB. It also defines the
- interface to the Registry/Repository being used by the engine. Typically the Synapse
- ESB is deployed between the actual client and a backend service implementation to
- mediate the message flow in between. Thus the Synapse ESB can accept a message
- on behalf of the actual service, perform authentication, validation, transformation,
- logging, routing based on the content etc. and then decide the destination target
- endpoint for the message and direct it to an actual service
+ interface to the Registry/Repository being used by the engine. Synapse Configuration is
+ now available with a XML Schema which defines the
+ <a href="./ns/2010/04/configuration/synapse_config.xsd">configuration language</a> using a set
+ of XSD's. Typically the Synapse ESB is deployed between the actual client and a back-end
+ service implementation to mediate the message flow in between. Thus the Synapse ESB can
+ accept a message on behalf of the actual service, perform authentication, validation,
+ transformation, logging, routing based on the content etc. and then decide the destination
+ target endpoint for the message and direct it to an actual service
implementation. The Synapse ESB can also detect timeouts, transport
failures during communication or introduce load balancing, throttling or
caching where necessary. For fault scenarios such as authentication