First of all, thanks for the answer and your time. I'm a big fan and there's not a single integration project I've developed during the past two years that doesn't use Camel :)
I had seen the 2.8 skipDuplicate option but decided not to use it anyway simply because I would end up with two repositories: the idempotent consumer one which only holds keys and my cache/map which would hold duplicate keys (with respect to the idempotent consumer's repository) and the message replies as values. I understand it isn't much difficult to code a solution using just a cache component. This is in fact what I've been doing so often that, from my point of view (which I understand is very limited), I thought it deserves a specific "component" (I know it wouldn't be a component in Camel terms, but bear with me :) ). >From what I see in the source code, what I would need to do is implement a repository similar to that which is used for the idempotent consumer, the only difference being the repository should store key/value pairs instead of just keys. Also, the "component" should be able to intercept the route's output (what you would see as the reply in an IN/OUT exchange) and store that as the value in the repository. Again, thanks for your time. Mirko -- View this message in context: http://camel.465427.n5.nabble.com/Idempotent-consumer-question-tp4510383p4514180.html Sent from the Camel - Users mailing list archive at Nabble.com.
