...
Options
Wiki Markup |
{div:class=confluenceTableSmall}
|| Name || Default Value || Description ||
| {{uri}} | | The URI of the endpoint to which the wire-tapped message will be sent. You should use either {{uri}} or {{ref}}. |
| {{ref}} | | Reference identifier of the endpoint to which the wire-tapped message will be sent. You should use either {{uri}} or {{ref}}. |
| {{executorServiceRef}} | | Reference identifier of a custom [Thread Pool|Threading Model] to use when processing the wire-tapped messages. If not set, Camel will use a default thread pool. |
| {{processorRef}} | | Reference identifier of a custom [Processor] to use for creating a new message (e.g., the "send a new message" mode). See below. |
| {{copy}} | {{true}} | *Camel 2.3*: Whether to copy the [Exchange] before wire-tapping the message. |
| {{onPrepareRef}} | | *Camel 2.8:* Reference identifier of a custom [Processor] to prepare the copy of the [Exchange] to be wire-tapped. This allows you to do any custom logic, such as deep-cloning the message payload. |
{div} |
...
Available as of Camel 2.8
See details at Multicast
Include Page |
|