You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@felix.apache.org by "Felix Meschberger (JIRA)" <ji...@apache.org> on 2007/10/02 13:54:50 UTC

[jira] Reopened: (FELIX-374) Register ManagedService on behalf of components to receive Configuration

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

Felix Meschberger reopened FELIX-374:
-------------------------------------


The implemented solution does not work for delayed and factory service components where the ComponentManager registers as a ServiceFactory on behalf of the real component. In this case, when accessing the ManagedService a new component instance is created instead of the ManagedService accessed.

The delayed and factory service ComponentManagers must not register themselves as ManagedService.

> Register ManagedService on behalf of components to receive Configuration
> ------------------------------------------------------------------------
>
>                 Key: FELIX-374
>                 URL: https://issues.apache.org/jira/browse/FELIX-374
>             Project: Felix
>          Issue Type: Improvement
>          Components: Declarative Services
>            Reporter: Felix Meschberger
>            Assignee: Felix Meschberger
>             Fix For: 1.0.0
>
>
> Currently the SCR calls the ConfigurationAdmin.getConfiguration(servicePid) method on behalf of components to retrieve configuration. If no such configuration exists, this call causes the creation of such configuration which is empty and may never ever be updated in case the component is not prepared to take Configuration from the Configuration Admin (perhaps there is nothing configurable in the component).
> The SCR should instead register a ManagedService on behalf of the component to receive configuration from the Configuration Admin as configuration becomes available. A good side effect of this is, that configuration provided to the component in this way has always passed the Configuration Admin plugins, which is not the case currently.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.