You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@felix.apache.org by "Frank Hölting (Jira)" <ji...@apache.org> on 2022/06/17 21:08:00 UTC

[jira] [Closed] (FELIX-6541) ConfigAdmin: Filter String without service.pid content

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

Frank Hölting closed FELIX-6541.
--------------------------------
    Resolution: Won't Fix

> ConfigAdmin: Filter String without service.pid content 
> -------------------------------------------------------
>
>                 Key: FELIX-6541
>                 URL: https://issues.apache.org/jira/browse/FELIX-6541
>             Project: Felix
>          Issue Type: Bug
>          Components: Configuration Admin
>            Reporter: Frank Hölting
>            Priority: Major
>
> In the version 1.9.24 I could see during debugging, that the component service.pid is not included in the filter string. The component property service.pid is no longer listed in the filter. 
> In the OSGi console the service.pid is still displayed as I expected.
> gogo: scr:list
>  ... 
> org.jcommand.wiring.JCommandWiringManagerComponent in bundle 34 (org.jcommand.wiring:1.0.0.202206162156) enabled, 1 instance.   
>  Id: 8, State:UNSATISFIED REFERENCE, PID(s): [org.jcommand.cm.persistencemanager.Wiring] 
> ...
>  
> In the SimpleFilter#compare method, the service.pid "org.jcommand.cm.persistencemanager.Wiring" is  compared with the component name from the SimpleFilter.
> PersistenceManagerProxy#getDictionaries(final SimpleFilter filter) Line 140 master commit f15d77759b0448a7456b9cfc067900c4f47a52e3 
> Or am I looking at the wrong place?



--
This message was sent by Atlassian Jira
(v8.20.7#820007)