I checked the osgi specification again. It seems if bundle location is null, only ManagedService of the first registered bundle will get the update event, the others cannot;
But the specification doesn't define another bundle cannot calling configAdmin.getConfiguration() to retrieve the configuration's properties; So why the application bundle invoke configAdmin.getConfiguration().getProperties() , but return a NULL properties ? I have confirmed application bundle only calling configAdmin.getConfiguration() just after admin bundle has updated the configuration. Does anyone know about it? Or My usage have offend the rules defined by the OSGI ConfigAdmin specification? Thanks any suggestion > -----original ----- > Sender: ext2 [mailto:[email protected]] > Date: 2011/6/27 11:46 > Receiver: [email protected] > Subject: Why OSGI Configuration is bound to a admin bundle temporary? > > Hi: > I have my own admin bundle which will deploy properties file as osgi > configuration , then deploy and start a application bundle associate with > the property file; > Most time, After the admin bundle update the OSGI configuration, the > application bundle will got the configuration's properties immediately at > start up time;. > But rarely, the application bundle must wait for about 4~5 seconds, > otherwise the application bundle can only get a null configuration > properties. > > Why? I have confirmed I have set the Bundle location to NULL in the > admin bundle, before starting the application bundle; > > Thanks any suggestion; > > > > > --------------------------------------------------------------------- > 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]
