-
1. Re: CamelContext and OsgiBundleXmlApplicationContext and clean-up/stop
davsclaus Sep 23, 2010 12:15 AM (in response to pchandler)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.
-
2. Re: CamelContext and OsgiBundleXmlApplicationContext and clean-up/stop
pchandler Sep 23, 2010 10:23 AM (in response to davsclaus)Claus,
Thanks. That answers my question.
Also, nice chatting with you at "FUSE Meet Up-Boston", August 17th 2010.
Peter.
-
3. Re: CamelContext and OsgiBundleXmlApplicationContext and clean-up/stop
pchandler Sep 23, 2010 11:25 AM (in response to davsclaus)BTW: From the "lifecycle page" the HTML link to the "Service" Interface seem to be broken. I found the link at Service
-
4. Re: CamelContext and OsgiBundleXmlApplicationContext and clean-up/stop
davsclaus Sep 23, 2010 1:43 PM (in response to pchandler)Thanks I have fixed the link.
Yeah it was a pleasure being in Boston and meeting real end users.
-
5. Re: CamelContext and OsgiBundleXmlApplicationContext and clean-up/stop
pchandler Oct 29, 2010 11:45 AM (in response to pchandler)For the record what "really" enable the spring destroy method processing is when I set:
OsgiBundleXmlApplicationContext osgiContext; //... osgiContext.registerShutdownHook();