Hi Or use a message filter and implement the logic to detect if the message id is still valid or not. http://camel.apache.org/message-filter.html
On Tue, May 26, 2015 at 9:42 AM, Willem Jiang <willem.ji...@gmail.com> wrote: > I’m afraid you have to implement your version of IdempotentRepository, as the > requirement is quite different. > > -- > Willem Jiang > > Red Hat, Inc. > Web: http://www.redhat.com > Blog: http://willemjiang.blogspot.com (English) > http://jnn.iteye.com (Chinese) > Twitter: willemjiang > Weibo: 姜宁willem > > > > On May 26, 2015 at 3:33:03 PM, noone100 (zaugg+ca...@puzzle.ch) wrote: >> Hi Willem >> >> Thanks for your answer! >> >> This filter should be able to skip out-of-order messages having the same >> correlation id but an older timestamp in a persistent manner, that's why I >> thought about a FileIdempotentRepository but this repo cannot track an id >> and a timestamp in conjunction. Is there another approach to store an id and >> a timestamp or is messaging the wrong technique for that problem and I >> should consider switching to a JPA based approach? >> >> >> >> -- >> View this message in context: >> http://camel.465427.n5.nabble.com/Discard-Obsolete-Messages-After-Redelivery-tp5767439p5767458.html >> Sent from the Camel - Users mailing list archive at Nabble.com. >> > -- Claus Ibsen ----------------- Red Hat, Inc. Email: cib...@redhat.com Twitter: davsclaus Blog: http://davsclaus.com Author of Camel in Action: http://www.manning.com/ibsen hawtio: http://hawt.io/ fabric8: http://fabric8.io/
