A service is either registered or not. There is no registered-but-you-can't-use-me-until-some-conditions-are-met state. So once bundle A observes service C being registered, bundle A can then register service B. It is up to the logic of bundle A to make this happen. Thinks like DS or Blueprint can manage these sorts of service dependencies on your behalf. --
BJ Hargrave Senior Technical Staff Member, IBM OSGi Fellow and CTO of the OSGi Alliance hargr...@us.ibm.com office: +1 386 848 1781 mobile: +1 386 848 3788 From: Peter Lauri <peterla...@gmail.com> To: osgi-dev@mail.osgi.org Date: 2010/11/30 11:16 Subject: [osgi-dev] Service dependencies Sent by: osgi-dev-boun...@mail.osgi.org Hi, If I have a bundle A that is providing a service B only if service C is available. Is it possible in the osgi framework to track these kind of dependencies/states. Bundle A will start perfectly fine and initially not publish any service as service C is not available in the system. Some other bundle D will after som time start and then publishes service C. At that point service B is published as service C was tracked. But before bundle D was started, could the service A then have an state of started but waiting for additional services to become a service provider? Maybe this is not fully clear, please let me know if this was completely not understandable. With regards, Peter Lauri * Sent on the road from my iPad _______________________________________________ OSGi Developer Mail List osgi-dev@mail.osgi.org https://mail.osgi.org/mailman/listinfo/osgi-dev
_______________________________________________ OSGi Developer Mail List osgi-dev@mail.osgi.org https://mail.osgi.org/mailman/listinfo/osgi-dev
