I guess another thing you could do is simply create a dummy service that's exposed using DS. If your dummy appears as a service in the OSGi Service Registry you know DS is running :)
2009/8/13 Neil Bartlett <[email protected]>: > Felix's SCR implementation registers an introspection service, > SCRService. The presence of that service will indicate that SCR is > running, and it can be used to query the state of the declarative > services, e.g. which ones are active, which are waiting for > dependencies, etc. > > Unfortunately, like Richard's suggestion of looking at the SCR bundle > state, this approach is specific to Felix. I would love to see the SCR > introspection API standardised in the spec. > > Regards, > Neil > > 2009/8/12 Richard S. Hall <[email protected]>: >> I am not sure if there is a standard way to do this. Conceptually, what you >> would need to do is track whether the DS bundle is ACTIVE or not, but there >> is no standard way to determine what this bundle is called. So, your only >> choice would be to hardcode the symbolic names of known DS bundles, I >> believe. >> >> -> richard >> >> On 8/12/09 4:33, André Dietisheim wrote: >>> >>> Hi! >>> >>> I try to implement a bundle that shall work whether DS is running or >>> not. In the latter case I'll register it's services and track >>> dependencies programmatically. >>> I discovered (in equinox) that DS registers a ConfigurationListener >>> service. I guess this is not reliable as there might be other components >>> that get registered as ConfigurationListener. >>> Tracking calls to bind/unbind-methods might not be suitable, too, if >>> there are no dependent services registered (I have a 0..n cardinality). >>> >>> I'd highly apprecaite any comments/hints! >>> Thanks in Advance + Cheers >>> André >>> >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: [email protected] >> For additional commands, e-mail: [email protected] >> >> > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
