Note that WSO2 EI is shipped with the following changes to what is mentioned in this documentation :
repository/samples/directory that includes all Integration profile samples is changed to
repository/samples/resources/directory that includes all artifacts related to the Integration profile samples is changed to
This sample demonstrates the use of dynamic keys with mediators. Here the XSLT Mediator is used to demonstrate the difference between the static and dynamic usage of keys.
For a list of prerequisites, see the prerequisites for starting the ESB samples.
Building the sample
The XML configuration for this sample is as follows:
This configuration file
synapse_sample_16.xml is available in the
To build the sample
Start the ESB with the sample 16 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_16.xml, the first registry resource
transform/transform.xslt is set as a property value.
Inside the XSLT mediator, the local property value is looked up using the Xpath expression
get-property(). Similarly, any XPath expression can be enclosed within curly braces to denote that it is a dynamic key. Then the mediator evaluates the real value for that expression.
The second XSLT resource
transform/transform_back.xslt is simply used as a static key. It is not included within curly braces since the mediator directly uses the static value as the key.
To execute the sample client
Run the following command from the
Analyzing the output
When you analyze the debug log output on the ESB console, you will see an output similar to that of Sample 8: Introduction to Static and Dynamic Registry Resources and Using XSLT Transformations.
You can try this sample with different local entries as the source with the correct target XPath values.