[
https://issues.apache.org/jira/browse/FELIX-714?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12670551#action_12670551
]
Pierre De Rop commented on FELIX-714:
-------------------------------------
Hello Felix,
I come back to you about this old problem of double reactivation (it's really
an issue for us).
So far, I have made the following patch in ImmediateComponentManager.java ->
public void reconfigure( Dictionary configuration )
{
// (Pierre) ignore initial configuration admin callback if there's not
configuration at all
if (configuration == null) {
return;
}
....
But I am not sure if this quick patch is really sufficient (probably not).
Do you plan to fix this issue ?
Thanks.
> Needless component reactivation on startup
> ------------------------------------------
>
> Key: FELIX-714
> URL: https://issues.apache.org/jira/browse/FELIX-714
> Project: Felix
> Issue Type: Bug
> Affects Versions: scr-1.0.0, scr-1.0.2, scr-1.0.4, scr-1.0.6
> Reporter: Felix Meschberger
> Priority: Minor
>
> SCR registers a ManagedService on behalf of each component to receive
> configuration from the Configuration Admin Service.
> During component activation, SCR executes the following steps:
> * registers a ManagedService on behalf of the Component
> * activates the Component
> * forwards configuration updates to the Component be reactivating it
> If on first component activation, the Configuration Admin Service has not yet
> updated the ManagedService the component will actually be activated twice:
> first without configuration and the second time with the configuration. If
> the Configuration Admin Service does not actually have configuration for the
> Component, the second activation is not needed and should be prevented.
> See also http://markmail.org/message/64kiv5nah4bc2ys4
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
