I'm too new to the Camel and ESB world to give a definitive answer to this, but I think those route managing capabilities are useful if Camel is running as a standalone application.
In my case, I don't need the integration and JBI capabilities of ServiceMix but only an easy way to define messaging routes. And as there are components in the application that are added or removed at runtime, I need to start or stop the corresponding routes at runtime as well. So I think it's good that there are methods in the Camel 2.0 API to this. M.S. Bruno Borges wrote: > > I'm sorry I'm getting this thread in the middle without reading previous > messages, but just one thought: isn't this what ESBs are supposed to > manage? > > I mean, with ESBs we can plug'n play routes easily, add, remove, whatever. > If Camel start to have functions like this, wouldn't be overlapping with > ESBs functions? > > How would Camel compare with ServiceMix for example? > > Please don't shoot. :-) > > Best regards, > Bruno Borges > blog.brunoborges.com.br > +55 21 76727099 > -- View this message in context: http://www.nabble.com/Starting%2C-stopping-and-removing-routes-at-runtime-tp22370230p22618396.html Sent from the Camel - Users (activemq) mailing list archive at Nabble.com.
