Hello Tom
Maybe you can tell us more about what you're doing and how you're doing
it. One of the benefits of DS is that it simplifies the registration of
OSGi services, but at the cost of losing some of the control over exactly
when a service is registered. If you're attempting to only register a
(parent) service when it has acquired all of its services, you might be
better off registering, and unregistering, the parent service "by hand"
using the OSGi APIs rather than using DS. You can do this easily from the
DS component's activate/deactivate methods.
Other thoughts:
- Are you using DS Factory Components to dynamically create DS components?
- Would creating multiple DS component that are enabled/disabled at
runtime be helpful to your problem?
If you can tell me more I might be able to provide you with further
recommendations. Also, DS is well covered in the following OSGi book (of
which I am one of the 3 authors):
http://equinoxosgi.org/
Good luck,
Simon
From:
Tom Kesling <[email protected]>
To:
OSGi Developer Mail List <[email protected]>
Date:
05/26/2010 02:55 PM
Subject:
[osgi-dev] ConfigurationAdmin question
Sent by:
[email protected]
Hello,
I'm using configurationadmin and ds to create service instances and
I'm trying to understand how to know when all of the instances have
been created.
There are parent to child relationships where a parent can have 0..n
children.
I don't want to start using a parent until all of it's children have
been created.
Does anyone have any advice on how to manage/approach this?
Thanks,
T
_______________________________________________
OSGi Developer Mail List
[email protected]
https://mail.osgi.org/mailman/listinfo/osgi-dev
_______________________________________________
OSGi Developer Mail List
[email protected]
https://mail.osgi.org/mailman/listinfo/osgi-dev
