OK - thanks. I guess I'll have to read the spec a bit better... In my case I have a factory configuration that instantiates component instances via iPOJO. I have a management bundle that reads the configurations (and presents them in a GUI) and also allows to change the configuration in some ways.
Am I then doing it correctly by using the two parameter version of "getConfiguration" and passing null as the second parameter? It seems that if I use the one parameter version, my management bundle "steals" the configuration from the original bundle. /Bengt 2013/11/11 Clement Escoffier <[email protected]> > Hi, > > In the 1.11.0, we changed how is handled the configuration admin to be > compliant with the configuration admin specification. > > Regards, > > Clement > > On 11 nov. 2013, at 12:53, Bengt Rodehav <[email protected]> wrote: > > > After some more research I changed the line: > > > > mConfigurationAdmin.getConfiguration(thePid); > > > > to > > > > mConfigurationAdmin.getConfiguration(thePid, null); > > > > The above line resides in the *se.digia.seco.web/web-service-plugin* > bundle > > referenced in the error message. > > > > I'm not exactly sure why it works and why the different versions of iPOJO > > behave differently in this respect. If someone can explain what is > > happening I would really appreciate it. > > > > /Bengt > > > > > > > > 2013/11/11 Bengt Rodehav <[email protected]> > > > >> I have just upgraded to iPOJO 1.11.0 from 1.8.6.and experience problems. > >> It seems like the binding of configurations don't work. I get the > following > >> error: > >> > >> *2013-11-11 12:32:46,450 | ERROR | 6f-684cbc7abeed) | ipojo > >> | ? ? | [ERROR] iPOJO > >> Configuration Admin listener : Cannot use configuration > >> pid=connect.generic.a7a9ebc6-0173-4a4a-b06f-684cbc7abeed for bundle > >> mvn:se.digia.connect.services.generic/service/2.6-SNAPSHOT because it > >> belongs to bundle mvn:se.digia.seco.web/web-service-plugin/1.7-SNAPSHOT* > >> > >> What might cause this to happen? I went back to iPOJO 1.8.6 and the > >> problem disappears immediately. Then when I change to iPojo 1.11.0 it > >> appears again. > >> > >> There is no conflict between persistent id's and everything works fine > >> when using iPOJO 1.8.6. Something must have changed. > >> > >> /Bengt > >> > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > >
