If you are working with queues you could send back to the message to the
first destination who will be your queue (or a failure/ dead-letter
queue) and process it again using an errorHandler for example.
On 4/02/2015 17:10, dbougie wrote:
I am trying to achieve an all or nothing, roll back all on exception when
using multicast. I have stopOnException enabled. My understanding however is
that this will just stop the continuing of processing/sending messages. If
the first delivery succeeded and the second failed then multicast would not
proceed to the third, but the first routing was already launched. Is there a
way to fail the whole works or roll back sending to the first destination
endpoint? I am not sure if parallelProcessing would be the answer that I am
looking for. I also was looking at shareUnitOfWork, but am not using a
compatible version of Camel. I know this is something that My boss really
wants so we can try re-sending failed messages through the same route
without creating issues.
--
View this message in context:
http://camel.465427.n5.nabble.com/All-or-Nothing-with-Multicast-tp5762393.html
Sent from the Camel - Users mailing list archive at Nabble.com.
