Camel is flexible and you can run it anyhow you like it. So if you run 1 route per camel context, or have N+ routes in the context, or have N context with 1 routes, or N context with N+ routes doesn't matter.
Its your choice. Though most people tend to have 1 context with N+ routes that is related, or belongs to the same business application. And you can add/remove routes at runtime. Just make sure to read a bit on the Camel website how to stop and remove routes. On Wed, Nov 27, 2013 at 1:09 PM, Chirag Dewan <[email protected]> wrote: > Hi All, > > > I am working on an application where we intend to use camel Endpoints for > most of the components for eg. FTP,SMPP,HTTP,Servlet,Jetty and many more. The > idea is to create separate wrapper components for all the endpoints and then > use them as libraries in our project. > > Now all my components will have separate Camel Contexts which will be > initialized from various modules in my project. > > > Secondly,each module needs to be scaled requiring multiple routes(multiple > endpoints per component). So I will dynamically add routes to my contexts. > > Is this the right way of doing things? > > I am pretty new to Camel,I believe there is something I am missing in the > above design. > > Please excuse my lack of knowledge. > > > Thanks! > > Chirag -- Claus Ibsen ----------------- Red Hat, Inc. Email: [email protected] Twitter: davsclaus Blog: http://davsclaus.com Author of Camel in Action: http://www.manning.com/ibsen
