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 2010/08/25 20:18:15 UTC

[jira] Resolved: (FELIX-2557) ConfigurationEvent delivery not building the listener list correctly

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

Felix Meschberger resolved FELIX-2557.
--------------------------------------

    Resolution: Fixed

Refactored ConfigurationEvent dispatching in Rev 989277:

  * The list of ConfigurationListener services to dispatch the event to is created synchronously with the actual Configuration.update/delete call
  * Event delivery is scheduled synchronously

Thus ConfigurationEvents are scheduled immediately before the configuration update/delete tasks.

> ConfigurationEvent delivery not building the listener list correctly
> --------------------------------------------------------------------
>
>                 Key: FELIX-2557
>                 URL: https://issues.apache.org/jira/browse/FELIX-2557
>             Project: Felix
>          Issue Type: Bug
>          Components: Configuration Admin
>    Affects Versions:  configadmin-1.2.4
>            Reporter: Felix Meschberger
>            Assignee: Felix Meschberger
>             Fix For:  configadmin-1.2.8
>
>
> According to the Configuration Admin Specification 1.3, Section 104.8 Configuration Events, the configuration events must be delivered "the same as described in Delivering Events on
> page 116 of the Core specification."
> This means, that :
>   - the list of interested ConfigurationListener services must be built at event creation time
>   - at event delivery time, all listeners must be called if their providing bundle is still active
> It is important to note, that listeners not registered at event creation time but registered at event delivery time must _not_ be called. On the other hand listeners registered at event creation time but unregistered at event delivery time must still be called (unless their providing bundle has been stopped).

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.