So that means I can create a bean in the blueprint and it will be picked up by the CamelContext? Wow, that was far simpler than I imagined. Thanks!
On 22 August 2014 00:54, Claus Ibsen <claus.ib...@gmail.com> wrote: > Hi > > See > > http://camel.apache.org/advanced-configuration-of-camelcontext-using-spring.html > > > On Fri, Aug 22, 2014 at 2:36 AM, Matt Sicker <boa...@gmail.com> wrote: > > I can't find anything anywhere about this, so I guess I have to ask here. > > I've got about ten different CamelContexts running in Karaf. After adding > > camel-disruptor, I've found that if I have to shut down Karaf, it hangs > for > > five minutes before finally letting go. I saw that this is the default > > settings for Camel, and the information about configuring the > > ShutdownStrategy are nonexistent. There's a brief mention of how to > obtain > > it from _a_ CamelContext, but I have no idea how that applies to the > other > > nine CamelContexts. > > > > How can I configure this so that it only waits for a few seconds before > > forceful termination? Since other services running in Karaf will have > > already shut down by this point, the fact that Camel is still accepting > > requests (CXF-RS) while claiming it can't shut down due to handling > > requests is complete nonsense as well. Every message it accepts times out > > due to no longer having an ActiveMQ connection. > > > > -- > > Matt Sicker <boa...@gmail.com> > > > > -- > Claus Ibsen > ----------------- > Red Hat, Inc. > Email: cib...@redhat.com > Twitter: davsclaus > Blog: http://davsclaus.com > Author of Camel in Action: http://www.manning.com/ibsen > hawtio: http://hawt.io/ > fabric8: http://fabric8.io/ > -- Matt Sicker <boa...@gmail.com>
