[HEADS UP] - Improved lifecycle and management of routes in Camel 2.5

Hi I am working a bit on improving the lifecycle and management of routes in Camel. The bigger goal is to support suspension of routes / camel. For example you can press suspend on CamelContext mbean and have it temporary suspend all routes. Then you can resume again by pressing resume, and the s

Re: [HEADS UP] - Improved lifecycle and management of routes in Camel 2.5

Hi Claus, I really like that, great work! Makes it easier to bind the lifecycle of routes to the lifecycle of components from other frameworks (e.g. to the lifecycle of Akka actors: these can be restarted and during a restart one might want to suspend routes to those actors). Cheers! Claus

Re: [HEADS UP] - Improved lifecycle and management of routes in Camel 2.5

Hi Claus, is it necessary to have a resume operation? I would propose to have only the start operation that can be called from stopped and from suspended state. Also I propose to allow the suspend command from stop to bring the route in a state where it can start faster. My proposed changes

Re: [HEADS UP] - Improved lifecycle and management of routes in Camel 2.5

On Mon, Aug 2, 2010 at 11:04 PM, Christian Schneider wrote: >  Hi Claus, > > is it necessary to have a resume operation? I would propose to have only the > start operation that can be called from stopped and from suspended state. > Also I propose to allow the suspend command from stop to bring the

Re: [HEADS UP] - Improved lifecycle and management of routes in Camel 2.5

Am 03.08.2010 06:04, schrieb Claus Ibsen: Yes you need to differentiate between resume/start in your business logic. The consumer most often need to different logic. For example a HTTP consumer may have to setup and start a HTTP server. Where as in resume it just need to accept requests instea

Re: [HEADS UP] - Improved lifecycle and management of routes in Camel 2.5

Christian Schneider wrote: Am 03.08.2010 06:04, schrieb Claus Ibsen: Yes you need to differentiate between resume/start in your business logic. The consumer most often need to different logic. For example a HTTP consumer may have to setup and start a HTTP server. Where as in resume it just

Re: [HEADS UP] - Improved lifecycle and management of routes in Camel 2.5

On Tue, Aug 3, 2010 at 10:30 PM, Christian Schneider wrote: > > > Am 03.08.2010 06:04, schrieb Claus Ibsen: >> >> Yes you need to differentiate between resume/start in your business logic. >> The consumer most often need to different logic. For example a HTTP >> consumer may have to setup and star