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

Posted to dev@felix.apache.org by "Felix Meschberger (JIRA)" <ji...@apache.org> on 2012/07/05 14:42:34 UTC

[jira] [Updated] (FELIX-3584) Handle new LOCATION_CHANGED event

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

Felix Meschberger updated FELIX-3584:
-------------------------------------

    Component/s: Specification compliance
    
> Handle new LOCATION_CHANGED event
> ---------------------------------
>
>                 Key: FELIX-3584
>                 URL: https://issues.apache.org/jira/browse/FELIX-3584
>             Project: Felix
>          Issue Type: Task
>          Components: Declarative Services (SCR), Specification compliance
>    Affects Versions: scr annotations 1.6.0
>            Reporter: Felix Meschberger
>
> Configuration Admin 1.5 adds a new configuration event type -- LOCATION_CHANGED=3 -- which is fired when the bundle location of a configuration is changed.
> The Felix SCR does not currently know this event and logs a WARN message if this event is fired. Instead of logging a WARN message, the LOCATION_CHANGED event should be handled to see whether the modified configuration has to be reassigned.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira