[jira] [Resolved] (SLING-5839) Implementation must not rely on SERVICE_PID

["Carsten Ziegeler (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/SLING-5839?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Carsten Ziegeler resolved SLING-5839.
-------------------------------------
    Resolution: Fixed

I've replaced the usage of SERVICE_PID in the composite health check, removed it as a property from the jmx bean and added the service id to the name of the meta data

> Implementation must not rely on SERVICE_PID
> -------------------------------------------
>
>                 Key: SLING-5839
>                 URL: https://issues.apache.org/jira/browse/SLING-5839
>             Project: Sling
>          Issue Type: Bug
>          Components: Health Check
>            Reporter: Carsten Ziegeler
>            Assignee: Carsten Ziegeler
>            Priority: Blocker
>             Fix For: Health Check Core 1.2.6
>
>
> The current implementation is relying in some places on the existince of the SERVICE_PID service property. However this is optional and an implementation detail.
> And the code currently only works as there is a long time bug in the maven scr plugin (FELIX-5304) which wrongly adds the SERVICE_PID to every component. 
> Therefore we must not rely on SERVICE_PID 



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)