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 >
