Hi, Am Mittwoch, den 08.06.2011, 06:07 +0100 schrieb Neil Bartlett: > Chris, > > The Felix SCR implementation offers a service interface > "org.apache.felix.scr.ScrService" that gives you an introspection API > for the state of DS components. > > I believe the Equinox DS implementation now offers the same service, > so it's becoming a kind of de facto standard, but I would also like to > see it become a real, specified standard API.
I once started on a new API which I intended to propose to the OSGi as the standard DS admin API [1]... But somehow this always was pushed back by some other work; I should pick this up again, probably ;-) Regards Felix [1] http://svn.apache.org/viewvc/felix/sandbox/fmeschbe/dsadmin/ > > Regards > Neil > > On Tue, Jun 7, 2011 at 10:44 PM, <[email protected]> wrote: > > Working with DS, I often feel the need to dig in and find out how the > > various components are getting along. Some frameworks have shell commands > > which allow one to examine the status of components (e.g. Felix, mBS) > > while others haven't or at least not yet (Knopflerfish). What I would > > most like though would be to design a probe which can inspect its > > environment and produce reports. Is there a (framework-independent) way > > to do this? Bundles and services are quite easy to enumerate and to track > > (race conditions aside), but components? Am I missing something? > > > > Best regards > > > > Chris > > > > > > _______________________________________________ > > 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 _______________________________________________ OSGi Developer Mail List [email protected] https://mail.osgi.org/mailman/listinfo/osgi-dev
