You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@felix.apache.org by "Thomas Watson (JIRA)" <ji...@apache.org> on 2015/01/06 16:14:34 UTC

[jira] [Updated] (FELIX-4753) Timing issues with bundle context configuration and CM configuration taking effect.

     [ https://issues.apache.org/jira/browse/FELIX-4753?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Thomas Watson updated FELIX-4753:
---------------------------------
    Attachment: FELIX-4753.patch

Possible fix by processing bundle context configuration first.

> Timing issues with bundle context configuration and CM configuration taking effect.
> -----------------------------------------------------------------------------------
>
>                 Key: FELIX-4753
>                 URL: https://issues.apache.org/jira/browse/FELIX-4753
>             Project: Felix
>          Issue Type: Bug
>          Components: Declarative Services (SCR)
>    Affects Versions: scr-2.0.0
>         Environment: All
>            Reporter: Thomas Watson
>         Attachments: FELIX-4753.patch
>
>
> In ScrConfiguration.start a ManagedService is registered in order to process configuration from CM.  The ManagedService is registered before processing configuration settings from the bundle context.  After registering the ManagedService the bundle context settings are processed synchronously.  The issue is that we do not know when a configuration will be delivered to the ManagedService.  It may happen synchronously as we are registering the ManagedService or later asynchronously or much later when CM is activated.  But the point is we don't have a predictable order here.
> I think we should have the configuration from CM override the bundle context property settings.  In order to do that we must guarantee that the bundle context properties are processed first so that later the CM configuration can override it.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)