This sample demonstrates how to use the Validate Mediator for XML schema validation and the usage of the local registry (local entries) for storing configuration metadata. Here a message is sent from the sample client to the back-end service through the ESB and shows how a static XML fragment could be made available to the ESB's local registry. It is assumed that the resources defined in the local registry are static (never changes over the lifetime of the configuration) and may be specified as a source URL, inline text or inline XML.
For a list of prerequisites, see Prerequisites to Start the ESB Samples.
Building the sample
The XML configuration for this sample is as follows:
This configuration file
synapse_sample_7.xml is available in the
To build the sample
Start the ESB with the sample 7 configuration. For instructions on starting a sample ESB configuration, see Starting the ESB with a sample configuration.
The operation log keeps running until the server starts, which usually takes several seconds. Wait until the server has fully booted up and displays a message similar to "WSO2 Carbon started in n seconds."
Start the Axis2 server. For instructions on starting the Axis2 server, see Starting the Axis2 server.
Deploy the back-end service SimpleStockQuoteService. For instructions on deploying sample back-end services, see Deploying sample back-end services.
Now you have a running ESB instance and a back-end service deployed. In the next section, we will send a message to the back-end service through the ESB using a sample client.
Executing the sample
The sample client used here is the Stock Quote Client, which can operate in several modes. For further details on this sample client and its operation modes, see Stock Quote Client.
According to the configuration file
synapse_sample_7.xml, the schema is made available under the validate_schema key. The Validate Mediator by default operates on the first child element of the SOAP body. You can specify an XPath expression using the
source attribute to override this behaviour. Here, the Validate Mediator uses the validate_schema resource to validate the incoming message and if the message validation fails, it invokes the on-fail sequence of mediators.
To execute the sample client
Run the following command from the
Analyzing the output
When you send the stock quote request, the schema validation fails and a fault is generated back with the message Invalid custom quote request. This is because the schema used in the example expects a slightly different message than what is created by the stock quote client. The schema used in the example expects a
stocksymbol element instead of
symbol to specify the stock symbol.