That is what I thought was the basis of doing OSGI. May be I did not do something correctly. I will try again and let you know. I have another question:
I am building two bundles. One creates the camel component to create a webservice client using CXF (webservice-client). The other one creates camel route from activemq to the webservice-client camel component (route-provisioner). When I specify require-bundle clause to the webservice-client POM definition, deploy the route and then invoke the client, it complains about missing org.apache.cxf.ProviderImpl. In this case even when I specified the dependency of webservice-client to CXF, it still does not take effect through the route-provisioner bundle. But when I specify same clause to route-provisioner pom.xml, it works correctly. In my application I am planning to eventually create camel context through JMX interface which means that I will not be able to specify dependencies then. Do you know how to get past this issue? Your help is highly appreciated. -- View this message in context: http://servicemix.396122.n5.nabble.com/Issue-with-executing-LTKJava-LLRP-protocol-library-inside-servicemix-4-due-to-dependency-on-apache-m7-tp5715372p5715412.html Sent from the ServiceMix - User mailing list archive at Nabble.com.
