Could you please describe more your situation and why a cold restart
would be needed? There may be other better solutions for your problem.
Cheers,
Hadrian
On 10/19/2012 03:51 PM, Daniel Gredler wrote:
Hi guys,
I was thinking about creating a feature request, but it involves such a
fundamental aspect of Camel that I thought I'd ask here first.
I have a situation where I'd like to do a cold restart on a Camel
context (context.stop(), and then context.start()). The catch is that I
want to do this via JMX, and when the Camel context is stopped, the JMX
service goes down and obviously I can't issue the start() request.
I was thinking that it would be nice to have a restart() method on the
Camel context (defined as the equivalent of stop + start), possibly even
in the Service interface which defines the start() and stop() methods.
This would allow the Camel context to go down and come back up without
requiring a second start() request, which is nice when the start()
request is impossible.
Is it worth creating the feature request? Am I missing something that
obviates the need for such a feature? Or is the use case so narrow that
it doesn't really make sense to add? Let me know what you think...
Take care,
Daniel
