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] Created: (FELIX-601) Reactivation of a component after a configuration update should be completely asynchronous
Date Fri, 06 Jun 2008 13:51:45 GMT
Reactivation of a component after a configuration update should be completely asynchronous
------------------------------------------------------------------------------------------

                 Key: FELIX-601
                 URL: https://issues.apache.org/jira/browse/FELIX-601
             Project: Felix
          Issue Type: Bug
          Components: Declarative Services (SCR)
    Affects Versions: scr-1.0.1
            Reporter: Felix Meschberger
            Assignee: Felix Meschberger
             Fix For: scr-1.0.1


Currently the component is taken down immediately upon receiving new configuration. This may
create issues when components are currently being activated. Therefore the cycling of the
component after receiving configuration is to be scheduled for asynchronous execution.

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