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] [Commented] (FELIX-3584) Handle new LOCATION_CHANGED event
Date Tue, 02 Apr 2013 15:11:15 GMT

    [ https://issues.apache.org/jira/browse/FELIX-3584?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13619908#comment-13619908
] 

David Jencks commented on FELIX-3584:
-------------------------------------

What I have now only works with a config admin with FELIX-3820 solved, not with any released
versions.
                
> 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-1.6.0
>            Reporter: Felix Meschberger
>            Assignee: David Jencks
>
> 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
For more information on JIRA, see: http://www.atlassian.com/software/jira

Mime
View raw message