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:28:31 UTC
svn commit: r1041706 -
/synapse/branches/2.0/src/site/xdoc/Synapse_Configuration_Language.xml
Author: ruwan
Date: Fri Dec 3 06:28:30 2010
New Revision: 1041706
URL: http://svn.apache.org/viewvc?rev=1041706&view=rev
Log:
Adding refs to individual schemas
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=1041706&r1=1041705&r2=1041706&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:28:30 2010
@@ -314,6 +314,7 @@
configuration parameters as may be required for the configuration of the
connection to the registry.
</p>
+ <p>Registry schema can be found at <a href="./ns/2010/04/configuration/registry.xsd">here</a></p>
<pre xml:space="preserve"> <registry provider="string"/>
<parameter name="string">text | xml</parameter>*
</registry></pre>
@@ -353,6 +354,7 @@
The <localEntry> element is used to declare registry entries that
are local to the Synapse instance, as shown below
</p>
+ <p>Local entry schema can be found at <a href="./ns/2010/04/configuration/local_entry.xsd">here</a></p>
<pre xml:space="preserve"> <localEntry key="string" [src="url"]>text | xml</localEntry></pre>
<p>
These entries are top level entries which are globally visible within the
@@ -401,6 +403,7 @@
mediation step. A tracing enabled sequence propagates this setting to
invoked sub-sequences.
</p>
+ <p>Sequence schema can be found at <a href="./ns/2010/04/configuration/sequence.xsd">here</a></p>
<pre xml:space="preserve"> <sequence name="string" [onError="string"] [key="string"] [trace="enable"]>
mediator*
</sequence></pre>
@@ -422,6 +425,7 @@ where "sequence/dynamic_seq_1.xml" refer
An endpoint may be specified as an address endpoint, WSDL based endpoint,
a load balancing endpoint or a fail-over endpoint as follows:
</p>
+ <p>Endpoint schema can be found at <a href="./ns/2010/04/configuration/endpoint.xsd">here</a></p>
<pre xml:space="preserve"><endpoint [name="string"] [key="string"]>
<a href="#address-endpoint">address-endpoint</a> | <a href="#default-endpoint">default-endpoint</a> | <a href="#wsdl-endpoint">wsdl-endpoint</a> | <a href="#load-balanced-endpoint">load-balanced-endpoint</a> | <a href="#fail-over-endpoint">fail-over-endpoint</a>
</endpoint> </pre>
@@ -715,6 +719,7 @@ where "sequence/dynamic_seq_1.xml" refer
<p>
A <proxy> element is used to define a Synapse Proxy service.
</p>
+ <p>Proxy service schema can be found at <a href="./ns/2010/04/configuration/proxy.xsd">here</a></p>
<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"]>
@@ -962,6 +967,7 @@ where "sequence/dynamic_seq_1.xml" refer
<p>
A <task> element is used to define a Synapse Startup Task.
</p>
+ <p>Task schema can be found at <a href="./ns/2010/04/configuration/task.xsd">here</a></p>
<pre xml:space="preserve"> <task class="mypackage.MyTask" name="string" [pinnedServers="(serverName)+"]>
<property name="stringProp" value="String"/>
<property name="xmlProp">
@@ -1003,6 +1009,7 @@ where "sequence/dynamic_seq_1.xml" refer
<p>
A <eventSource> element is used to define a Synapse event source.
</p>
+ <p>Event source schema can be found at <a href="./ns/2010/04/configuration/event_source.xsd">here</a></p>
<pre xml:space="preserve"><eventSource name="string">
<subscriptionManager class="mypackage.MyClass">
<parameter name="string"/>
@@ -1039,6 +1046,7 @@ where "sequence/dynamic_seq_1.xml" refer
mediator allows Apache BSF scripts such as Javascript, Ruby, Groovy etc to
be used for mediation.
</p>
+ <p>All mediator schema can be found at <a href="./ns/2010/04/configuration/mediators/">here</a></p>
<h3>
Core Mediators
</h3>