Hi I have a situation where I process create and update events for various business objects, customer for example. The create event may fail when invoking a remote webservice and then the message goes to a dead_letter queue. All good so far.
However, all subsequent update events related to the same customer can not be handled by the system since the create event was not fully processed. The remote webservice fails silently in this situation and the update events are simply consumed i.e. lost. How do I avoid that the "update events" gets processed, and goes to the remote webservice, before the "create event" succedes? I think this must be a common problem and some of you clever people must have solved this in an elegant manner ;-) In general terms, I am looking for a solution that guarantees that the correct sequence of related messages are obeyed even in the case when one of these messages fails (then they should all fail). TIA Henrik -- View this message in context: http://camel.465427.n5.nabble.com/Advice-much-appreciated-tp5743213.html Sent from the Camel - Users mailing list archive at Nabble.com.
