[jira] [Resolved] (FELIX-6026) SCR command problems

["Thomas Watson (JIRA)" <ji...@apache.org>]

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

Thomas Watson resolved FELIX-6026.
----------------------------------
       Resolution: Fixed
    Fix Version/s: scr-2.1.16

Will be fixed in 2.1.16 release.

> SCR command problems
> --------------------
>
>                 Key: FELIX-6026
>                 URL: https://issues.apache.org/jira/browse/FELIX-6026
>             Project: Felix
>          Issue Type: Bug
>          Components: Declarative Services (SCR)
>    Affects Versions: scr-2.1.14
>            Reporter: Brent Daniel
>            Priority: Major
>             Fix For: scr-2.1.16
>
>
> There are a couple of problems resulting from the changes to SCR commands in [https://github.com/apache/felix/pull/130] .
> First, ScrInfo is not registered as a service when ds.info.service=true is specified in config admin. The core issue is that the setScrCommand method of ScrConfigurationImpl is never called, so it will not be available in this block around line 208:
> {code:java}
> if ( scrCommand != null )
> {
> scrCommand.updateProvideScrInfoService( infoAsService() );
> }
> {code}
> That can be fixed by adding the following to the Activator.doStart() method (though I haven't spent much time thinking about better solutions):
> {code:java}
> m_configuration.setScrCommand(m_componentCommands);
> {code}
> Second, the ScrInfo list() and info() implementation no longer accept a null component ID. The javadoc for ScrInfo still indicates that a null ID will give information for all components. We have found this function invaluable for dumping the state of every component, so it would be nice to get this back.
>  



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)