You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@synapse.apache.org by ch...@apache.org on 2007/04/23 08:34:41 UTC
svn commit: r531350 -
/webservices/synapse/trunk/java/src/site/resources/Synapse_Configuration_Language.html
Author: chathura_ce
Date: Sun Apr 22 23:34:41 2007
New Revision: 531350
URL: http://svn.apache.org/viewvc?view=rev&rev=531350
Log:
Added the timeout configuration to the synapse configuration language documentation.
Modified:
webservices/synapse/trunk/java/src/site/resources/Synapse_Configuration_Language.html
Modified: webservices/synapse/trunk/java/src/site/resources/Synapse_Configuration_Language.html
URL: http://svn.apache.org/viewvc/webservices/synapse/trunk/java/src/site/resources/Synapse_Configuration_Language.html?view=diff&rev=531350&r1=531349&r2=531350
==============================================================================
--- webservices/synapse/trunk/java/src/site/resources/Synapse_Configuration_Language.html (original)
+++ webservices/synapse/trunk/java/src/site/resources/Synapse_Configuration_Language.html Sun Apr 22 23:34:41 2007
@@ -19,36 +19,6 @@
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
- <meta content="text/html; charset=iso-8859-1">
- <meta content="text/html; charset=iso-8859-1">
- <meta content="text/html; charset=iso-8859-1">
- <meta content="text/html; charset=iso-8859-1">
- <meta content="text/html; charset=iso-8859-1">
- <meta content="text/html; charset=iso-8859-1">
- <meta content="text/html; charset=iso-8859-1">
- <meta content="text/html; charset=iso-8859-1">
- <meta content="text/html; charset=iso-8859-1">
- <meta content="text/html; charset=iso-8859-1">
- <meta content="text/html; charset=iso-8859-1">
- <meta content="text/html; charset=iso-8859-1">
- <meta content="text/html; charset=iso-8859-1">
- <meta content="text/html; charset=iso-8859-1">
- <meta content="text/html; charset=iso-8859-1">
- <meta content="text/html; charset=iso-8859-1">
- <meta content="text/html; charset=iso-8859-1">
- <meta content="text/html; charset=iso-8859-1">
- <meta content="text/html; charset=iso-8859-1">
- <meta content="text/html; charset=iso-8859-1">
- <meta content="text/html; charset=iso-8859-1">
- <meta content="text/html; charset=iso-8859-1">
- <meta content="text/html; charset=iso-8859-1">
- <meta content="text/html; charset=iso-8859-1">
- <meta content="text/html; charset=iso-8859-1">
- <meta content="text/html; charset=iso-8859-1">
- <meta content="text/html; charset=iso-8859-1">
- <meta content="text/html; charset=iso-8859-1">
- <meta content="text/html; charset=iso-8859-1">
- <meta content="text/html; charset=iso-8859-1">
<meta content="text/html; charset=iso-8859-1" http-equiv="content-type">
<title>Synapse Configuration Language</title>
</head>
@@ -97,8 +67,7 @@
<p>The <localEntry> element is used to declare registry entries that
are local to the Synapse instance, as shown below</p>
-<pre> <localEntry key="string" [src="url"]>text | xml</localEntry>
-</pre>
+<pre> <localEntry key="string" [src="url"]>text | xml</localEntry></pre>
<p>These entries are top level entries which are set globally for the entire
system. Values of these entries can be retrieved via the extension XPath
@@ -117,8 +86,7 @@
can be invoked later by name as a sequence of mediators.</p>
<pre> <sequence name="string" [onError="string"] [key="string"]>
mediator*
- </sequence>
-</pre>
+ </sequence></pre>
<p>If the configuration defines a sequence named "main" then it is considered
as the main mediation sequence of Synapse. If such a sequence is not defined
@@ -157,14 +125,21 @@
</endpoint></pre>
<h4>Address Endpoint</h4>
-<p>An address-endpoint token refers to an endpoint address definition as follows:</p>
+
+<p>An address-endpoint token refers to an endpoint address definition as
+follows:</p>
<pre><address uri="endpoint-address" format="soap|soap11|soap12|pox" [optimize="mtom|swa"]>
<enableRM [policy="key"]/>?
<enableSec [policy="key"]/>?
<enableAddressing/>?
+ <timeout>
+ <duration>timeout-duration<duration>
+ <action>discard|fault</action>
+ </timeout>?
</address></pre>
<h4>WSDL Endpoint</h4>
+
<p>A wsdl-endpoint token refers to a WSDL endpoint definition as follows:</p>
<pre><wsdl [uri="wsdl-uri"] [service="qname"] [port/endpoint="qname"]>
<wsdl:definition>...</wsdl:definition>?
@@ -172,22 +147,36 @@
<enableRM [policy="key"]/>?
<enableSec [policy="key"]/>?
<enableAddressing/>?
+ <timeout>
+ <duration>timeout-duration</duration>
+ <action>discard|fault</action>
+ </timeout>?
</wsdl></pre>
-<p>The WSDL could be defined in-line within the endpoint definition or as a uri reference and the service & port/endpoint specified if multiple options are present.</p>
+
+<p>The WSDL could be defined in-line within the endpoint definition or as a
+uri reference and the service & port/endpoint specified if multiple
+options are present.</p>
<h4>Load balanced Endpoint</h4>
-<p>A load-balanced-endpoint token refers to a load balancing configuration from which the destination endpoint would be selected depending on the evaluation of the current message against the load balacing algorithm</p>
+
+<p>A load-balanced-endpoint token refers to a load balancing configuration
+from which the destination endpoint would be selected depending on the
+evaluation of the current message against the load balacing algorithm</p>
<pre><loadBalance policy="string">
<endpoint .../>+
</loadBalance></pre>
<h4>Failover Endpoint</h4>
-<p>A fail-over-endpoint token refers to a fail-over configuration definition from which an endpoint is selected if the sending of a message to the endpoint results in a failure</p>
+
+<p>A fail-over-endpoint token refers to a fail-over configuration definition
+from which an endpoint is selected if the sending of a message to the
+endpoint results in a failure</p>
<pre><failOver policy="string">
<endpoint .../>+
</failover></pre>
-<p>An endpoint definition must name the endpoint, and a dynamic endpoint lookup must specify the key for a definition.</p>
+<p>An endpoint definition must name the endpoint, and a dynamic endpoint
+lookup must specify the key for a definition.</p>
<h3>Proxy service</h3>
@@ -485,8 +474,7 @@
<p>A script mediator using a entry (registry or local) is defined as
follows:</p>
-<pre> <script key="string" language="string" [function="script-function-name"]/>
-</pre>
+<pre> <script key="string" language="string" [function="script-function-name"]/></pre>
<p>The property-key is a Synapse registry property containing a URL to the
script source. Optional language attribute specifies the scripting language
@@ -501,8 +489,7 @@
<p>An inline script mediator has the script source embedded in the config
XML:</p>
-<pre> <script language="string">...script source code...<script/>
-</pre>
+<pre> <script language="string">...script source code...<script/></pre>
<p>where language is the script language name extension. For example,
<script language="js"> indicates a JavaScript program, <script
@@ -513,8 +500,7 @@
<p>An example of an inline mediator using JavaScript/E4X which returns false
if the SOAP message body contains an element named 'symbol' which has a value
of 'IBM' would be:</p>
-<pre> <script language="js">mc.getPayloadXML()..symbol != "IBM";<script/>
-</pre>
+<pre> <script language="js">mc.getPayloadXML()..symbol != "IBM";<script/></pre>
<p>The boolean response from the inlined mediator is either the response from
the evaluation of the script statements or if that result is not a boolean
---------------------------------------------------------------------
To unsubscribe, e-mail: synapse-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: synapse-dev-help@ws.apache.org