Wow... a context for a context... brain explodes. I didn't know this was here I'll have a deeper look once my brain is back in one piece ;-)
--jason On Jan 8, 2012, at 5:08 AM, Willem Jiang wrote: > You can have a look at the camel-context component[1]. It maybe useful for > you have a try :) > > [1]http://camel.apache.org/context.html > > On 1/8/12 7:53 AM, Jason Dillon wrote: >> I'm wondering what the best practice is for a complex application, where >> many sub-systems (some related, some not) are using camel to process >> messages, if it is best to have all of them share the same single >> CamelContext or if its better to have more than one CamelContext to >> partition the systems? >> >> Any advise? >> >> --jason > > > -- > Willem > ---------------------------------- > FuseSource > Web: http://www.fusesource.com > Blog: http://willemjiang.blogspot.com (English) > http://jnn.javaeye.com (Chinese) > Twitter: willemjiang > Weibo: willemjiang
