Author: hiranya Date: Tue Jul 7 02:20:37 2009 New Revision: 40924 URL: http://wso2.org/svn/browse/wso2?view=rev&revision=40924
Log: Minor changes to the Synapse configuration language guide Modified: branches/esb/java/2.1/product/docs/xdoc/configuration_language.xml Modified: branches/esb/java/2.1/product/docs/xdoc/configuration_language.xml URL: http://wso2.org/svn/browse/wso2/branches/esb/java/2.1/product/docs/xdoc/configuration_language.xml?rev=40924&r1=40923&r2=40924&view=diff ============================================================================== --- branches/esb/java/2.1/product/docs/xdoc/configuration_language.xml (original) +++ branches/esb/java/2.1/product/docs/xdoc/configuration_language.xml Tue Jul 7 02:20:37 2009 @@ -173,7 +173,7 @@ are served through the built-in Registry. When using the Registry to hold pieces of the configuration, certain elements such as endpoint definitions, sequences and local entries could be updated dynamically while the Synapse ESB -executes, the the Registry could trigger a re-load as configured. </p> +is executing, and the Registry could trigger a re-load as configured. </p> <h2>The Synapse Configuration (synapse.xml) </h2> @@ -197,8 +197,8 @@ <p>The Synapse ESB can operate in two modes: </p> -<h3><a href="#service_mediation">Service mediation</a> / <a href="#proxy">Proxy -services</a> </h3> +<h3>Service mediation / Proxy +services </h3> <p>In Service mediation, the Synapse ESB exposes a service endpoint on the ESB, that accepts messages from clients. Typically these services acts as proxies @@ -213,7 +213,7 @@ or SOAP, POX, Plain Text or Binary / Legacy service for other transports such as JMS and VFS file systems - e.g. CSV content being the payload </p> -<h3><a>Message mediation</a> </h3> +<h3>Message mediation</h3> <p>In Message mediation, Synapse can act as a transparent proxy for clients - if they are directed to point to the Synapse ESB as a http proxy. This way, @@ -553,6 +553,10 @@ <td></td> <td><tt>vfs:ftp://guest:gu...@localhost/directory?vfs.passive=true</tt></td> </tr> + <tr> + <td>FIX</td> + <td><tt>fix://localhost:9876?BeginString=4.4&SenderCompID=SYNAPSE&TargetCompID=EXEC</tt></td> + </tr> </tbody> </table> @@ -1131,7 +1135,7 @@ <ul> <li>body - The SOAP 1.1 or 1.2 body element </li> For example; expression="$body/getQuote" refers to the first getQuote element - in the SOAP body regardless of whether the message is SOAP-11 or SOAP-12 + in the SOAP body regardless of whether the message is SOAP-11 or SOAP-12 <li>header - The SOAP 1.1 or 1.2 header element </li> For example; expression="$header/wsa:To" refers to the addressing To header regardless of whether this message is SOAP-11 or SOAP-12 </ul> @@ -1367,7 +1371,7 @@ mediator can be configured to continue or to stop the mediation after the routing by setting the 'continueAfter' attribute value to be 'true' and 'false' respectively. Each and every route must contain an 'expression' attribute which -is to specify the XPath over which the roting condition is evaluated. Apart +is to specify the XPath over which the routing condition is evaluated. Apart from that there can be an optional 'match' attribute as well. If both expression and the match attirbutes are specified in a particualr route, the evaluated string value of the XPath over the current message will be campared @@ -1377,7 +1381,7 @@ considered as the routing condition. </p> <p>One can configure a route to break routing or continue evaluating further -routes to see any further matchings by setting the 'breakRoute' attribute to +routes to see any further matchings by setting the 'breakRouter' attribute to 'true' or 'false' respectively. For all the routes there has to be a 'target' element which contains the information about the routing path as a sequence or an endpoint both can be inlined as well as refered. If both an endpoint and a _______________________________________________ Esb-java-dev mailing list [email protected] https://wso2.org/cgi-bin/mailman/listinfo/esb-java-dev
