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 2010/08/26 09:18:52 UTC

[jira] Created: (FELIX-2558) Handle configuration changes without restarting event admin service

Handle configuration changes without restarting event admin service
-------------------------------------------------------------------

                 Key: FELIX-2558
                 URL: https://issues.apache.org/jira/browse/FELIX-2558
             Project: Felix
          Issue Type: Improvement
          Components: Event Admin
    Affects Versions: eventadmin-1.2.2
            Reporter: Carsten Ziegeler
            Assignee: Carsten Ziegeler
             Fix For: eventadmin-1.2.4


Currently, when the configuration for the event admin is updated, the old event admin service is unregistered and a new service is started and registered.
We can handle this configuration update internally without the need to unregister and reregister.

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


[jira] Resolved: (FELIX-2558) Handle configuration changes without restarting event admin service

Posted by "Carsten Ziegeler (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/FELIX-2558?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Carsten Ziegeler resolved FELIX-2558.
-------------------------------------

    Resolution: Fixed

changed the implementation in revision 991190 - this is a first test implementation

> Handle configuration changes without restarting event admin service
> -------------------------------------------------------------------
>
>                 Key: FELIX-2558
>                 URL: https://issues.apache.org/jira/browse/FELIX-2558
>             Project: Felix
>          Issue Type: Improvement
>          Components: Event Admin
>    Affects Versions: eventadmin-1.2.2
>            Reporter: Carsten Ziegeler
>            Assignee: Carsten Ziegeler
>             Fix For: eventadmin-1.2.4
>
>
> Currently, when the configuration for the event admin is updated, the old event admin service is unregistered and a new service is started and registered.
> We can handle this configuration update internally without the need to unregister and reregister.

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


[jira] Resolved: (FELIX-2558) Handle configuration changes without restarting event admin service

Posted by "Carsten Ziegeler (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/FELIX-2558?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Carsten Ziegeler resolved FELIX-2558.
-------------------------------------

    Resolution: Fixed

The first implementation looks good, therefore resolving this issue

> Handle configuration changes without restarting event admin service
> -------------------------------------------------------------------
>
>                 Key: FELIX-2558
>                 URL: https://issues.apache.org/jira/browse/FELIX-2558
>             Project: Felix
>          Issue Type: Improvement
>          Components: Event Admin
>    Affects Versions: eventadmin-1.2.2
>            Reporter: Carsten Ziegeler
>            Assignee: Carsten Ziegeler
>             Fix For: eventadmin-1.2.4
>
>
> Currently, when the configuration for the event admin is updated, the old event admin service is unregistered and a new service is started and registered.
> We can handle this configuration update internally without the need to unregister and reregister.

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


[jira] Closed: (FELIX-2558) Handle configuration changes without restarting event admin service

Posted by "Carsten Ziegeler (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/FELIX-2558?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Carsten Ziegeler closed FELIX-2558.
-----------------------------------


> Handle configuration changes without restarting event admin service
> -------------------------------------------------------------------
>
>                 Key: FELIX-2558
>                 URL: https://issues.apache.org/jira/browse/FELIX-2558
>             Project: Felix
>          Issue Type: Improvement
>          Components: Event Admin
>    Affects Versions: eventadmin-1.2.2
>            Reporter: Carsten Ziegeler
>            Assignee: Carsten Ziegeler
>             Fix For: eventadmin-1.2.4
>
>
> Currently, when the configuration for the event admin is updated, the old event admin service is unregistered and a new service is started and registered.
> We can handle this configuration update internally without the need to unregister and reregister.

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


[jira] Reopened: (FELIX-2558) Handle configuration changes without restarting event admin service

Posted by "Carsten Ziegeler (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/FELIX-2558?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Carsten Ziegeler reopened FELIX-2558:
-------------------------------------


> Handle configuration changes without restarting event admin service
> -------------------------------------------------------------------
>
>                 Key: FELIX-2558
>                 URL: https://issues.apache.org/jira/browse/FELIX-2558
>             Project: Felix
>          Issue Type: Improvement
>          Components: Event Admin
>    Affects Versions: eventadmin-1.2.2
>            Reporter: Carsten Ziegeler
>            Assignee: Carsten Ziegeler
>             Fix For: eventadmin-1.2.4
>
>
> Currently, when the configuration for the event admin is updated, the old event admin service is unregistered and a new service is started and registered.
> We can handle this configuration update internally without the need to unregister and reregister.

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