But I did install the Camel feature, but it does not contain camel-core-osgi!
So the only way to kickstart Camel in Karaf is by using blueprint? I do not want Spring or any XML configuration files, well blueprint seems inevitable. Regards, Borut Sent from my iPad On 13. apr. 2012, at 16:55, Claus Ibsen <claus.ib...@gmail.com> wrote: > Hi > > I suggest to install the camel feature, and not camel-core. By install > camel feature, you get Camel support for Spring-DM and Blueprint. > Then you should be able to install and start your bundle out of the box. > > If you use another Camel component such as FTP, Velocity etc. Then you > need to install those features beforehand as well. > > > On Fri, Apr 13, 2012 at 12:33 PM, Borut Bolčina <borut.bolc...@gmail.com> > wrote: >> OK, I installed the latest Karaf (2.2.6) and Camel features with >> >> features:chooseurl camel 2.9.1 >> >> >> features:install camel-core >> >> >> Then I installed my bundle into the local maven repo and then to Karaf with >> >> karaf@root> osgi:install >> mvn:com.mycompany/route-weather-current/1.0-SNAPSHOT >> Bundle ID: 67 >> >> As I suspected, this bundle will have difficulities to start up, as I did >> not install all the neccessary features into Karaf needed by my bundle and >> so the error happens: >> >> karaf@root> osgi:start 67 >> org.osgi.framework.BundleException: Unresolved constraint in bundle >> route-weather-current-osgi [67]: Unable to resolve 67.0: missi >> ng requirement [67.0] package; >> (&(package=org.apache.camel.core.osgi)(version>=2.9.0)(!(version>=3.0.0))) >> >> As I am using camel-core-osgi and this feature is not installed with >> features:chooseurl camel 2.9.1 where do I get it? >> >> Thanks, >> borut >> >> Dne 11. april 2012 10:46 je Claus Ibsen <claus.ib...@gmail.com> napisal/-a: >> >>>> The blueprint.xml file is then placed in the META-INF/blueprint >>>> directory. The standard place for that. >>> >>> Ah sorry I think its OSGI-INF/blueprint/blueprint.xml >>> >>> The name of the XML file dont have to be blueprint.xml. I think you >>> can name it myapp.xml, camel.xml, etc. Or what you like. >>> >>> Anyway the point is its the whatever the blueprint standard is. >>> >>> >>> >>> >>> >>> -- >>> Claus Ibsen >>> ----------------- >>> CamelOne 2012 Conference, May 15-16, 2012: http://camelone.com >>> FuseSource >>> Email: cib...@fusesource.com >>> Web: http://fusesource.com >>> Twitter: davsclaus, fusenews >>> Blog: http://davsclaus.blogspot.com/ >>> Author of Camel in Action: http://www.manning.com/ibsen/ >>> > > > > -- > Claus Ibsen > ----------------- > CamelOne 2012 Conference, May 15-16, 2012: http://camelone.com > FuseSource > Email: cib...@fusesource.com > Web: http://fusesource.com > Twitter: davsclaus, fusenews > Blog: http://davsclaus.blogspot.com/ > Author of Camel in Action: http://www.manning.com/ibsen/
