You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@felix.apache.org by "Carsten Ziegeler (JIRA)" <ji...@apache.org> on 2012/07/13 15:29:36 UTC
[jira] [Created] (FELIX-3596) Config Admin should track
SynchronousConfigurationListeners
Carsten Ziegeler created FELIX-3596:
---------------------------------------
Summary: Config Admin should track SynchronousConfigurationListeners
Key: FELIX-3596
URL: https://issues.apache.org/jira/browse/FELIX-3596
Project: Felix
Issue Type: Bug
Components: Configuration Admin
Affects Versions: configadmin-1.6.0
Reporter: Carsten Ziegeler
Fix For: configadmin-1.6.0
According to the 5.0 enterprise spec (104.8) synchronous configuration listeners register themselves with the SCL interface. Verified by BJ :)
The current implementation in trunk expects them to register with the CL interface.
(Even if a SCL registers as a CL it should be treated just like a CL)
--
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
[jira] [Assigned] (FELIX-3596) Config Admin should track
SynchronousConfigurationListeners
Posted by "Felix Meschberger (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/FELIX-3596?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Felix Meschberger reassigned FELIX-3596:
----------------------------------------
Assignee: Felix Meschberger
> Config Admin should track SynchronousConfigurationListeners
> -----------------------------------------------------------
>
> Key: FELIX-3596
> URL: https://issues.apache.org/jira/browse/FELIX-3596
> Project: Felix
> Issue Type: Bug
> Components: Configuration Admin
> Affects Versions: configadmin-1.6.0
> Reporter: Carsten Ziegeler
> Assignee: Felix Meschberger
> Fix For: configadmin-1.6.0
>
>
> According to the 5.0 enterprise spec (104.8) synchronous configuration listeners register themselves with the SCL interface. Verified by BJ :)
> The current implementation in trunk expects them to register with the CL interface.
> (Even if a SCL registers as a CL it should be treated just like a CL)
--
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
[jira] [Commented] (FELIX-3596) Config Admin should track
SynchronousConfigurationListeners
Posted by "Felix Meschberger (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/FELIX-3596?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13414321#comment-13414321 ]
Felix Meschberger commented on FELIX-3596:
------------------------------------------
Thanks for reporting.
For reference the discussion on OSGi-dev: https://mail.osgi.org/pipermail/osgi-dev/2012-July/003530.html
> Config Admin should track SynchronousConfigurationListeners
> -----------------------------------------------------------
>
> Key: FELIX-3596
> URL: https://issues.apache.org/jira/browse/FELIX-3596
> Project: Felix
> Issue Type: Bug
> Components: Configuration Admin
> Affects Versions: configadmin-1.6.0
> Reporter: Carsten Ziegeler
> Fix For: configadmin-1.6.0
>
>
> According to the 5.0 enterprise spec (104.8) synchronous configuration listeners register themselves with the SCL interface. Verified by BJ :)
> The current implementation in trunk expects them to register with the CL interface.
> (Even if a SCL registers as a CL it should be treated just like a CL)
--
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
[jira] [Work started] (FELIX-3596) Config Admin should track
SynchronousConfigurationListeners
Posted by "Felix Meschberger (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/FELIX-3596?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Work on FELIX-3596 started by Felix Meschberger.
> Config Admin should track SynchronousConfigurationListeners
> -----------------------------------------------------------
>
> Key: FELIX-3596
> URL: https://issues.apache.org/jira/browse/FELIX-3596
> Project: Felix
> Issue Type: Bug
> Components: Configuration Admin
> Affects Versions: configadmin-1.6.0
> Reporter: Carsten Ziegeler
> Assignee: Felix Meschberger
> Fix For: configadmin-1.6.0
>
>
> According to the 5.0 enterprise spec (104.8) synchronous configuration listeners register themselves with the SCL interface. Verified by BJ :)
> The current implementation in trunk expects them to register with the CL interface.
> (Even if a SCL registers as a CL it should be treated just like a CL)
--
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
[jira] [Resolved] (FELIX-3596) Config Admin should track
SynchronousConfigurationListeners
Posted by "Felix Meschberger (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/FELIX-3596?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Felix Meschberger resolved FELIX-3596.
--------------------------------------
Resolution: Fixed
Fixed in Rev. 1361527 by having separate service trackers for Synchronous and regular ConfigurationListener services. Only services registered as SynchronousConfigurationListener services are called synchronously.
Also enhanced the tests to verify SynchronouseConfigurationListener implementations registered as ConfigurationListeners are called asynchronously.
> Config Admin should track SynchronousConfigurationListeners
> -----------------------------------------------------------
>
> Key: FELIX-3596
> URL: https://issues.apache.org/jira/browse/FELIX-3596
> Project: Felix
> Issue Type: Bug
> Components: Configuration Admin
> Affects Versions: configadmin-1.6.0
> Reporter: Carsten Ziegeler
> Assignee: Felix Meschberger
> Fix For: configadmin-1.6.0
>
>
> According to the 5.0 enterprise spec (104.8) synchronous configuration listeners register themselves with the SCL interface. Verified by BJ :)
> The current implementation in trunk expects them to register with the CL interface.
> (Even if a SCL registers as a CL it should be treated just like a CL)
--
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
[jira] [Closed] (FELIX-3596) Config Admin should track
SynchronousConfigurationListeners
Posted by "Felix Meschberger (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/FELIX-3596?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Felix Meschberger closed FELIX-3596.
------------------------------------
> Config Admin should track SynchronousConfigurationListeners
> -----------------------------------------------------------
>
> Key: FELIX-3596
> URL: https://issues.apache.org/jira/browse/FELIX-3596
> Project: Felix
> Issue Type: Bug
> Components: Configuration Admin
> Affects Versions: configadmin-1.6.0
> Reporter: Carsten Ziegeler
> Assignee: Felix Meschberger
> Fix For: configadmin-1.6.0
>
>
> According to the 5.0 enterprise spec (104.8) synchronous configuration listeners register themselves with the SCL interface. Verified by BJ :)
> The current implementation in trunk expects them to register with the CL interface.
> (Even if a SCL registers as a CL it should be treated just like a CL)
--
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