Hi,
Yes, that was the right thing to do. If you build a bundle that depends on features that are not installed by default, those will have to be installed manually first. Afterwards, you can drop the bundle in the deploy folder. You could also write a features.xml file which lists your bundle as well as those required features to get them all installed automatically. Have a look at http://karaf.apache.org/manual/latest-2.3.x/users-guide/provisioning.html For this particular example, the README.txt file says to use "features:install examples-activemq-camel-blueprint" to install the example, so that would install both the actual example JAR as well as the required features for you. Regards, Gert Vanthienen On Mon, May 12, 2014 at 5:46 PM, techy_bolek <[email protected]> wrote: > I did: > > features:install camel:jms > > And this seemed to take care of the problem. > > Was that the right thing to do? > > > > > -- > View this message in context: > http://servicemix.396122.n5.nabble.com/java-lang-NoClassDefFoundError-org-apache-camel-component-jms-JmsComponent-tp5720228p5720230.html > Sent from the ServiceMix - User mailing list archive at Nabble.com.
