Author: hiranya
Date: Mon May 3 11:35:34 2010
New Revision: 940422
URL: http://svn.apache.org/viewvc?rev=940422&view=rev
Log:
Fixing SYNAPSE-391. Documentation update. (Patch from Heshan)
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=940422&r1=940421&r2=940422&view=diff
==============================================================================
--- synapse/trunk/java/src/site/xdoc/Synapse_Configuration_Language.xml
(original)
+++ synapse/trunk/java/src/site/xdoc/Synapse_Configuration_Language.xml Mon May
3 11:35:34 2010
@@ -1997,6 +1997,18 @@ where "sequence/dynamic_seq_1.xml" refer
as follows:
</p>
<pre xml:space="preserve"> <script language="string">...script source
code...<script/></pre>
+
+<p>
+ If the script you specified is calling a function defined in another
script,
+ then the latter script should also be included in the script mediator
+ configuration. It's done using the <include> element. The key
attribute of the
+ <include> element should point to the script which has to be
included. The included
+ script could be stored as a local entry or in the remote registry.
+ Script includes are defined as follows:
+ </p>
+<pre xml:space="preserve"> <script key="string" language="string"
[function="script-function-name"]>
+ <include key="string"/>
+ </script></pre>
<p>
The execution context environment of the script has access to the Synapse
MessageContext predefined in a script variable named 'mc' . An example of