[
https://issues.apache.org/jira/browse/FELIX-2368?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12873177#action_12873177
]
Felix Meschberger commented on FELIX-2368:
------------------------------------------
Committed a first shot in Rev. 949317.
All enablement, activation, deactivation, and disablement is now done
synchronously. The only asynchronous executions being the
ComponentContext.enable(String) and .disable(String) methods, which are
required to activate and deactivate, resp., the named components.
> Activate components synchronously
> ---------------------------------
>
> Key: FELIX-2368
> URL: https://issues.apache.org/jira/browse/FELIX-2368
> Project: Felix
> Issue Type: Improvement
> Components: Declarative Services (SCR)
> Affects Versions: scr-1.4.0
> Reporter: Felix Meschberger
> Assignee: Felix Meschberger
> Fix For: scr-1.4.2
>
>
> Currently components are activated asynchronously. This works perfect but
> adds delay to startup sequences. An additional problem is that on system
> startup once the FRAMEWORK_STARTED event is received, SCR is still busy
> activating components. This creates a problem if we want to decide on the
> actual system state.
> Conversely, disposal (and disabling) of components always takes place
> immediately, because either a required dependency is about to go away or the
> providing bundle is stopped. In the first case asynchronous disabling will
> lead to problems because of unavailable services and the second case might
> cause IllegalStateExceptions if the BundleContext is accessed after the
> 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.
