...
Option | Default | Description |
---|---|---|
eager | true | Eager controls whether Camel adds the message to the repository before or after the exchange has been processed. If enabled before then Camel will be able to detect duplicate messages even when messages are currently in progress. By disabling Camel will only detect duplicates when a message has successfully been processed. |
messageIdRepositoryRef |
| A reference to a |
skipDuplicate | true | Camel 2.8: Sets whether to skip duplicate messages. If set to |
removeOnFailure | true | Camel 2.9: Sets whether to remove the id of an Exchange that failed. |
scope | OnCompletion | Camel 2.16: Sets the scope of this idempotent consumer where its boundaries ends. The default mode is OnCompletion which means the idempotent consumer will only trigger its completion at the end of the routing of the exchange, when the exchange completes. So if the exchange is continued routed after the block ends, then whatever happens there also affect the state. For example if the exchange failed due to an exception, then the state of the idempotent consumer will be a rollback. The other mode BlockOnly means that the idempotent consumer will trigger its completion when the exchange reached the end of the block of the idempotent consumer pattern. So if the exchange is continued routed after the block ends, then whatever happens there does not affect the state. |
Using the Fluent Builders
The following example will use the header myMessageId to filter out duplicates
...