Name
Wire Tap — Routes a copy of a message to a secondary destination while passing the original message to the actual recipient
Usage
The wire tap pattern makes a copy of the message exchange and directs the copy to a secondary location. The original exchange continues to the next step in the route.
The wire tap pattern can be placed anywhere in the route body.
Properties
Table 3.20 describes the properties you can specify using the properties editor.
Table 3.20. Wire Tap Properties
| Name | Description |
|---|---|
| New Exchange Expression | Specifies the expression used to determine the contents of the new message exchange. |
| language | Specifies the expression language used to process the expression. |
| Uri | Specifies the URI of the endpoint to which the copy is routed. See Table of Components in Component Reference for a list of valid URI patterns. |
| New Exchange Processor Ref | Specifies a reference to a bean implementing a message processor to process the original message before it is passed to the next step in the route. |
| Copy | Specifies if the original message is copied into the new message. |
| Executor Service Ref | Specifies a reference for looking up the
executorService to use for
thread pool management. |
| Id | Specifies a unique identifier for the endpoint. The Id can be used to refer to the endpoint in the Apache Camel configuration file. |
| Description | Specifies a text description of the bean. The description is included in the generated XML file. |
Related topics
| Expression and Predicates Languages |
| Configuring the Fuse IDE route editor in Using Fuse IDE |
 |  |  |
 |
