I think the Wire Tap would be a good candidate for your case http://camel.apache.org/wire-tap.html May be you can combine it also with a RoutePolicy to notify for begin/completed statuses
Bilgin On 20 February 2012 15:21, Gert Villemos <gville...@yahoo.de> wrote: > I have a route that is invoked by a user through a GUI. The route may > easily > take 2-3 hours to complete. > > I would like to send back notifications to the user, showing him the > progress (... and that something is happening). The route has 4 processors. > > I have until now been using a second route as 'return' route, into which > each processor send messages. It is however not very clean; the processors > needs to 'know' the return route. > > I would prefer a solution where the route results in multiple, asynchronous > return messages, where the last is a 'completed' status. > > Is there a common way of doing this? > > -- > View this message in context: > http://camel.465427.n5.nabble.com/Returning-status-messages-tp5499371p5499371.html > Sent from the Camel - Users mailing list archive at Nabble.com. >
