Hi, 1.- The moment I deploy my routes,I don't want to start them, what I want is to be able to instantiate them from another bundle as many times as i want and start them from there, is this possible?? >> By default, a bundle having its dependencies (= packages to be imported) is >> started automatically when deployed on Apache ServiceMix. Nevertheless, it >> is perfectly possible to deploy without to start it and having a separate >> application deployed in another bundle which will take care about >> stopping/starting bundles containing camel routes. Camel routes can also be stopped/started/resumed or scheduled. So you can also consider to use an external application which will manage them. The management of the Camel routes deployed could be made using JMX api as you will be able to have access to the CamelContext and their routes.
2.- Sorry if this one is too basic. Every time i instantiate one of my routes, i want to send it some parameters before starting it, i was thinking in sending my values on the constructor to some instance members and then proceed to start. This sounds very simple but i really don't know if i can do this with a camel osgi, so, is this possible? >> They are 2 solutions that you can use - 1) camel - propoerties >> (http://camel.apache.org/properties.html) or 2) OSGI config admin >> (http://static.springsource.org/osgi/docs/1.2.x/reference/html/compendium.html). >> Both approaches uses the concept of Spring PropertyPlaceHolder 3.- Do all my routes have to be on the same camel-context?? >> No but they will need to be interconnected using direct:// or seda:// >> (within the same bundle) or using nmr:// (between bundles) Regards, Charles Moulliard Apache Committer Blog : http://cmoulliard.blogspot.com Twitter : http://twitter.com/cmoulliard Linkedin : http://www.linkedin.com/in/charlesmoulliard Skype: cmoulliard On Wed, Jul 20, 2011 at 4:57 PM, rogelio_sevilla1 <[email protected]> wrote: > Hello everyone: > > I'm starting a project where i've been asked to use servicemix (more > precisely, fuse esb) and camel. I came up with a design, however, i'm not > 100% sure if it can be done because i have a couple of doubts about the > behaviour of camel as an osgi bundle. I have to deploy my camel routes on > fuse esb and i was wondering if you can help me to answer these questions. > > > 1.- The moment I deploy my routes,I don't want to start them, what I want is > to be able to instantiate them from another bundle as many times as i want > and start them from there, is this possible?? > > > 2.- Sorry if this one is too basic. Every time i instantiate one of my > routes, i want to send it some parameters before starting it, i was thinking > in sending my values on the constructor to some instance members and then > proceed to start. This sounds very simple but i really don't know if i can > do this with a camel osgi, so, is this possible? > > > 3.- Do all my routes have to be on the same camel-context?? > > > > Thanks a lot for your time and i really appreciate any advice you could give > me. > > > -- > View this message in context: > http://camel.465427.n5.nabble.com/Camel-and-Osgi-doubt-tp4616189p4616189.html > Sent from the Camel - Users mailing list archive at Nabble.com. >
