I'd prefer to create new contexts because it's a multi-tenant app and I'd like a little separation between the routes of each client. If it's not possible, I can work within a single context, it's just not ideal.
Chris On Wed, Dec 19, 2012 at 10:59 AM, Christian Müller < [email protected]> wrote: > Do you really need to create new Camel context's? > Why it's not enough to "only" create new routes? > > Best, > Christian > > On Wed, Dec 19, 2012 at 3:08 PM, Chris Geer <[email protected]> wrote: > > > We are building a system running on top of Karaf and have a need for one > of > > our OSGI services to be able to dynamically create new camel contexts and > > routes. I thought I could get away with just creating a new > > DefaultCamelContext but I'm running into a lot of problems with component > > resolution (among other things). After some research I came across the > > OSGIDefaultCamelContext however that seems to be embedded in the > > camel-blueprint and camel-spring bundles and not directly accessible. We > > are using blueprint but I didn't think manually creating blueprint > contexts > > was the right solution either. > > > > If I create my context/route in a blueprint file it all works fine, I > just > > need to figure out how to create them dynamically. > > > > Camel 2.10.3 > > > > Thanks, > > Chris > > > > > > -- >
