RE: Cannot use configuration pid ... for bundle XX because it belongs to bundle YY

>> The main bundle activator does the following regarding this component: >> Dictionary properties = new Hashtable> Object>(); properties.put("userRolesFile", "someFileSystemPath"); >> properties.put("userCredentialsFile", "someFileSystemPath"); >>

Re: Cannot use configuration pid ... for bundle XX because it belongs to bundle YY

null works, ds < 2.0.4 will (except for unusual situations not likely here) set the bundle location to the using bundle, ds >-2.0.4 will leave it null. This will “claim” the configuration for the using bundle. ? works with a R5+ config admin and multiple bundles can use the configuration.

Re: Cannot use configuration pid ... for bundle XX because it belongs to bundle YY

> Carsten, are you sure about null and not the literal string "?" Hi, both work - if you have a configuration admin supporting multi locations (the "?"). But as that is in there for some time, you probably have it. null works in any case and does not change the location at all - that's why I

Re: Cannot use configuration pid ... for bundle XX because it belongs to bundle YY

Carsten, are you sure about null and not the literal string "?" - Ray On Wed, Aug 10, 2016 at 9:57 AM, Carsten Ziegeler wrote: > > Did not find any annotation in those components, they actually get > configured using the ConfigurationAdmin. > > > > Error: > > >

Re: Cannot use configuration pid ... for bundle XX because it belongs to bundle YY

> Did not find any annotation in those components, they actually get configured > using the ConfigurationAdmin. > > Error: > pid=com.kuka.authorizationService.component for bundle 7 because it belongs > to bundle 77> > > OSGI-LIB\*.xml: > http://www.osgi.org/xmlns/scr/v1.1.0; >

RE: Cannot use configuration pid ... for bundle XX because it belongs to bundle YY

Did not find any annotation in those components, they actually get configured using the ConfigurationAdmin. Error: OSGI-LIB\*.xml: http://www.osgi.org/xmlns/scr/v1.1.0; activate="activate" configuration-policy="require" deactivate="deactivate" immediate="true"

Re: Cannot use configuration pid ... for bundle XX because it belongs to bundle YY

In my experience, it means that you have annotated two different classes with @Component and specified the same configurationPid. You can't do that; if you need to share a configuration between DS components, you have to inject the ConfigurationAdmin service instead of using the @Component