felix-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "David Jencks (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (FELIX-3875) [DS] After configuration changes target filter on optional ref, matching services are not bound
Date Sun, 10 Feb 2013 07:53:13 GMT

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

David Jencks updated FELIX-3875:
--------------------------------

    Fix Version/s:     (was: scr-1.6.4)
                   scr-1.8.0
    
> [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.8.0
>
>
> 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

Mime
View raw message