To be clear, DS == Declarative Services.
The core OSGi API allows you to manually track service dependencies, but
does not automate this process for you. For automated service dependency
tracking, you need a service-oriented component framework, like DS,
iPOJO, or Blueprint.
-> richard
On 11/30/10 11:20, Jeff McAffer wrote:
DS should do this just fine. Declare a component for B and say it needs C.
Not sure what you meant about *service* A being started but... Did you mean
*bundle* A? Assuming yes, the topic here is not so much which bundles are
started but which DS components are activated.
Make sense or did I misunderstand?
Jeff
On 2010-11-30, at 11:08 AM, Peter Lauri wrote:
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
_______________________________________________
OSGi Developer Mail List
osgi-dev@mail.osgi.org
https://mail.osgi.org/mailman/listinfo/osgi-dev
