[jira] Commented: (FELIX-601) Reactivation of a component after a configuration update should be completely asynchronous

["Felix Meschberger (JIRA)" <ji...@apache.org>]

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

Felix Meschberger commented on FELIX-601:
-----------------------------------------

Implemented completely asynchronous cycling after configuration update in Rev. 663943

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