Replying to myself here: since this doesn't seem to ring a bell with anyone, should I file a bug?
--- On Mon, 2/22/10, Ulf Dittmer <[email protected]> wrote: > From: Ulf Dittmer <[email protected]> > Subject: ServiceListener: Changes between ConfigAdmin 1.0 and 1.2? > To: [email protected] > Date: Monday, February 22, 2010, 6:07 AM > Hello everyone- > > I have a ServiceListener that stores a service reference to > the ConfigAdmin service when that's started, something like this: > > public void serviceChanged (ServiceEvent event) { > > String[] objectClass = (String[]) > event.getServiceReference().getProperty(Constants.OBJECTCLASS); > > if (event.getType() == > ServiceEvent.REGISTERED) { > if > (objectClass[0].equals(ConfigurationAdmin.class.getName())) > { > ServiceReference > servRef = context.getServiceReference(objectClass[0]); > > ConfigurationAdmin configAdmin = (ConfigurationAdmin) > context.getService(servRef); > > etc. > > That worked fine using ConfigAdmin 1.0.10, which causes the > listener to be called twice, one each for > org.apache.felix.cm.PersistenceManager and > org.osgi.service.cm.ConfigurationAdmin. > > But ConfigAdmin 1.2.4 causes it to be called only once for > org.apache.felix.cm.PersistenceManager, thus causing my app > not to be aware of the newly installed ConfigAdmin. I'd like > the code to be free of references to specific Felix classes, > so my questions are: Is this a bug? Can the previous > behavior be restored? Or should the code be doing something > differently? > > Thanks, > Ulf --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
