On Thu, Mar 2, 2017 at 9:42 AM, Mestiri Meher <meher.mest...@gmail.com> wrote: > Correct me if I'm wrong but I think the steps are the following : > > 1/ wrap the dependencies into wrappes. > 2/ install them as bundles into the felix. > 3/ make those bundles start oncethe felix starts. > Following this I'm having an issue with an sl4j logger dependency : > "slf4j.simple_1.6.1.jar" > and the error is that I can not start the bundle.. > "org.osgi.framework.BundleException: Fragment bundles can not be started."
I do not know about sfl4j. But you have step 3 incorrect, you do not have to start every bundle, just install them. If you have a bundle which just provide some code you just install it, and the server will resolve and use it when other started bundle needs it. And, specifically, you do not start fragments, you start ( if needed ) the host. > Could you please let me know if I'm following the right scenario and if you > have an idea on how I could resolve the slf4j dependency. Try to just install it without starting. For debugging I some times RESOLVE them after instaling ( just to force any resolution errors there instead of delaying them, as they normally indicate missing dependencies and those are easier to deal with when you are in the install-bundles-mindset. Francisco Olarte. _______________________________________________ OSGi Developer Mail List osgi-dev@mail.osgi.org https://mail.osgi.org/mailman/listinfo/osgi-dev
