...
| Info |
|---|
The Event mediator is a content-aware mediator. |
...
| Table of Contents | ||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
...
| Code Block | ||||
|---|---|---|---|---|
| ||||
<event xmlns="http://ws.apache.org/ns/synapse" topic="" [expression=""] /> |
...
UI Configuration
The configuration options parameters available for configuring the Event Mediator mediator are as follows:
| Parameter Name | Description |
|---|---|
| Topic Type | The type of topic. The available options are as follows.
|
...
| |
| Topic | The topic to which the events |
...
should be published. |
...
You can |
...
enter a static |
...
value or an XPath expression based on the option you selected for the Topic Type parameter.
| ||||||
| Expression | The XPath expression used to build the message to be published to the specified topic.
|
| Info | ||
|---|---|---|
| ||
You can configure the Mediator mediator using XML. Click on " switch to source view " in the "Mediator" window.
|
...
Examples
In this example, when an event notification comes to the EventingProxy proxy service, they are processed by the PublicEventSource sequence, which logs the messages and publishes them to the topic SampleEventSource. Services that subscribe to the topic SampleEventSource will then receive these messages.
| Code Block | ||||
|---|---|---|---|---|
| ||||
<!-- Simple Eventing configuration -->
<definitions xmlns="http://ws.apache.org/ns/synapse">
<sequence name="PublicEventSource" >
<log level="full"/>
<event topic="SampleEventSource"/>
</sequence>
<proxy name="EventingProxy">
<target inSequence="PublicEventSource" />
</proxy>
</definitions>
|
In this scenario, when an event notification comes to the EventingProxy proxy service, they are processed by the PublicEventSource sequence, which logs the messages and publishes them to the topic SampleEventSource. Services that subscribe to the topic SampleEventSource will then receive these messages.
...
Sample
See the following sample for another example.