CamelContext and OsgiBundleXmlApplicationContext and clean-up/stop

[pchandler]

For OSGi Activator.start() I do a:

OsgiBundleXmlApplicationContext applicationContext = new OsgiBundleXmlApplicationContext(aSpringCamelContextFile);
applicationContext.setBundleContext(bundleContext);
applicationContext.setPublishContextAsService(false);
applicationContext.refresh();

For OSGi Activator.stop() I do a:

applicationContext.stop();

My question is, my spring camel context file has components/endpoints that have external references (examples., JMS, JDBC connections). When I call the stop() method on the context how do all the components/endpoints  get notified?  Is there a recursive process, some type of interface to implement, registered listeners?

Additionally, if I create my own camel component how do I get called/invoked when the camel context is stopped?

Thanks in advance,

Peter.

[davsclaus]

For the Camel component you can take a look at the lifecycle page at

http://camel.apache.org/lifecycle.html

So you custom component should just implement the Service interface in Camel and you have callbacks for start and stop.

If you component extend DefaultComponent then it should already implement the Service. The idea is then you can override the doStart / doStop methods.

[pchandler]

Claus,

Thanks. That answers my question. 

Also, nice chatting with you at "FUSE Meet Up-Boston", August 17th 2010.

Peter.

[pchandler]

BTW: From the "lifecycle page" the HTML link to the "Service" Interface seem to be broken. I found the link at Service

[davsclaus]

Thanks I have fixed the link.

Yeah it was a pleasure being in Boston and meeting real end users.

[pchandler]

For the record what "really" enable the spring destroy method processing is when I set:

 
OsgiBundleXmlApplicationContext osgiContext;
//...
osgiContext.registerShutdownHook();