I can’t think of any circumstances where you’d want to register with the system bundle, normally you’d register with the bundle interested in the configuration. It won’t make any difference unless you are using framework hooks to control service visibility. An example of where it would make a difference is if you installed a bunch of isolated subsystems each containing their own config admin implementation. Registering the listener with a bundle in one of these subsystems will make it visible only to that subsystem’s config admin. Depending on how the isolation is set up registering with the system bundle is likely to make it invisible to all the subsystem config admins or possibly visible to all of them.
out of curiosity, why do you need your own ConfigurationListener? thanks david jencks > On Aug 10, 2016, at 2:02 PM, Benson Margulies <[email protected]> wrote: > > I see examples that seem to be just registering these as a service on > any old bundle. The javadoc says, "ConfigurationListener objects are > registered with the Framework service registry". Does that mean the > system bundle? > > --------------------------------------------------------------------- > 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]
