[jira] [Resolved] (SLING-6650) osgi-mock: Fallback to component name when service.pid property not set in SCR metadata

["Stefan Seifert (JIRA)" <ji...@apache.org>]

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

Stefan Seifert resolved SLING-6650.
-----------------------------------
    Resolution: Fixed

rev. 1787072 (2.x)
rev. 1787073 (1.x)

> osgi-mock: Fallback to component name when service.pid property not set in SCR metadata
> ---------------------------------------------------------------------------------------
>
>                 Key: SLING-6650
>                 URL: https://issues.apache.org/jira/browse/SLING-6650
>             Project: Sling
>          Issue Type: Bug
>          Components: Testing
>    Affects Versions: Testing OSGi Mock 1.9.2, Testing OSGi Mock 2.2.2
>            Reporter: Stefan Seifert
>            Assignee: Stefan Seifert
>              Labels: mocks
>             Fix For: Testing OSGi Mock 2.2.4, Testing OSGi Mock 1.9.4
>
>
> with ConfigAdmin it is possible to provide a configuration for a OSGi component registered in mock context via it's PID.
> depending on certain circumstances (e.g. bnd version) the SCR metadata contains a service.pid property or not. if it is not set we should use the component name instead for matching it when setting configuration via ConfigAdmin.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)