Unfortunately its not the repository I've extended, its the consumer itself.
On Feb 11, 2014 10:30 PM, "Christian Müller"
wrote:
> Instead of
> class="org.apache.camel.processor.idempotent.MemoryIdempotentRepository"/>
>
> you should configure your own IdempotentRepository.
>
> Best,
>
> Christi
Instead of
you should configure your own IdempotentRepository.
Best,
Christian
-
Software Integration Specialist
Apache Member
V.P. Apache Camel | Apache Camel PMC Member | Apache Camel committer
Apache Incubator PMC Member
https://www.linkedin.com/pub/christian-mueller/11/55
Hi,
Unless I am mistaken this just adds a the standard IdempotentConsumer to
the route? This would remove messages with duplicate keys indefinatly. I
only want to remove them while the duplicate message is being processed.
Or am I missing something?
Thanks,
Sam
On 11 February 2014 21:43, Chri
See [1] for details.
http://camel.apache.org/schema/spring";>
messageId
[1] http://camel.apache.org/idempotent-consumer.html
Best,
Christian
-
Software Integration Specialist
Apache Mem
Hi,
I want to extend the IdempotentConsumer to only deny duplicated while the
duplicate message is being processed.
My plan was to add an additional Synchronization that removed the messageId
from the repository when the message has finished processing. However I
can't find a simple example of ho
