Hi Atanas,
> However, the usage of this EIP requires modification of the original route
> (insertion of an idempotentConsumer instruction before every destination
> endpoint) and I would prefer to use an alternative approach (if it's
> possible).
Why would modifying the route (e.g. inserting idem
Hi Richard,
thanks for your prompt reply.
It looks like the Idempotent Consumer might help, especially if in it's
File/JDBC based implementations the message ids are durably persisted (it
seems quite logical to be so), so that they are available after a JVM
restart for example.
However, the usag
Your use case it slightly different then the standard use case but perhaps
the Idempotent Consumer will suit your needs?
http://camel.apache.org/idempotent-consumer.html
On Tue, Jan 21, 2014 at 2:12 PM, shindito wrote:
> Hi guys,
>
> consider the following route:
>
> from(srcEndpoint).
> to(des
