What about usage of PIDs when providing configurations through the repository (as sling:OsgiConfig resources or configuration files as described in https://sling.apache.org/documentation/bundles/configuration-installer-factory.html <https://sling.apache.org/documentation/bundles/configuration-installer-factory.html>) for the OSGi installer. The resource names are supposed to be (at least starting with the) PID, e.g. mentioned in https://sling.apache.org/documentation/bundles/osgi-installer.html <https://sling.apache.org/documentation/bundles/osgi-installer.html> and https://sling.apache.org/documentation/bundles/configuration-installer-factory.html Is this really the PID here? Is there some cleaning in order on the documentation or the implementation side for the OSGi Installer as well?
I am wondering though, why only the PID is exposed in system/console/services/xxx and not the service id. Konrad > On 13 Jul 2016, at 12:07, Carsten Ziegeler <[email protected]> wrote: > >> On Wed, Jul 13, 2016 at 8:01 AM, Carsten Ziegeler <[email protected]> >> wrote: >>> ...We really have to fix our code and get rid of most of the usage of >>> PIDs... >> >> And use SERVICE_ID instead when we need a unique key to the service? >> > Yes, right > > Btw, I fixed the health check core bundle, not sure which others need to > be fixed. But I guess the list is really short > > Regards > > Carsten > > -- > Carsten Ziegeler > Adobe Research Switzerland > [email protected] >
