felix-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Felix Meschberger (JIRA)" <j...@apache.org>
Subject [jira] Commented: (FELIX-2557) ConfigurationEvent delivery not building the listener list correctly
Date Thu, 26 Aug 2010 08:49:53 GMT

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

Felix Meschberger commented on FELIX-2557:
------------------------------------------

Further refined configuraiton event dispatching in Rev. 989533: Configuration events and configuration
updates are now dispatched in two separate threads (grouped in a daemon ThreadGroup). This
allows for quick event delivery to listeners not being "blocked" by configuration updates.

> 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.


Mime
View raw message