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

Posted to dev@felix.apache.org by "David Jencks (JIRA)" <ji...@apache.org> on 2013/02/03 02:58:12 UTC

[jira] [Resolved] (FELIX-3875) [DS] After configuration changes target filter on optional ref, matching services are not bound

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

David Jencks resolved FELIX-3875.
---------------------------------

    Resolution: Fixed

Fixed with rev 1439755 (test) and 1439756 (fix)
                
> [DS] After configuration changes target filter on optional ref, matching services are not bound
> -----------------------------------------------------------------------------------------------
>
>                 Key: FELIX-3875
>                 URL: https://issues.apache.org/jira/browse/FELIX-3875
>             Project: Felix
>          Issue Type: Bug
>          Components: Declarative Services (SCR)
>    Affects Versions: scr-1.6.4
>            Reporter: David Jencks
>            Assignee: David Jencks
>             Fix For: scr-1.6.4
>
>
> Given an optional reference in a component, and a created component instance, if you change the target filter with a config admin configuration change, newly matching services are not bound.
> The problem is that the new ServiceTracker is not activated.
> There's a related problem that no-longer-matching services are not unbound.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira