...
A WireTap component can be used to forward a copy of the input message to a listener in a proxy fashion.
This component implements the WireTap pattern.
It can handle all four standard MEPs, but will only send an In-Only MEP to the listener.
The originating service must be configured to send messages to the WireTap directly.
In the case of an In-Out MEP, this means that the WireTap needs to be configured to send the exchange along to the destination service.
This doc need to be update - it seems that wire tap can also be used to forward fault and out messages. See also wire tap xml schema
Wiki Markup |
---|
{snippet:id=wire-tap|lang=xml|url=servicemix/smx3/trunk/deployables/serviceengines/servicemix-eip/src/test/resources/org/apache/servicemix/eip/spring.xml} |
...
Code Block | ||||
---|---|---|---|---|
| ||||
<eip:resequencer
service="sample:Resequencer"
endpoint="ResequencerEndpoint"
comparator="#comparator"
capacity="100"
timeout="2000">
<eip:target>
<eip:exchange-target service="sample:SampleTarget" />
</eip:target>
</eip:resequencer>
<!-- Configure default comparator with custom sequence number property -->
<eip:default-comparator id="comparator" sequenceNumberKey="seqnum"/>
|
...