[
https://issues.apache.org/jira/browse/FELIX-374?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Felix Meschberger closed FELIX-374.
-----------------------------------
Resolution: Fixed
Not the ImmediateComponentManager itself is registered as a ManagedService but
an instance of an anonymous class, which forwards the updated configuration to
the reconfigure(Dictionary) method of the ImmediateComponentManager.
The former ImmediateComponentManager.updated method is renamed to reconfigure
to prevent a name collision with the ManagedService.updated method.
Fixed in Rev. 581211.
Deployed fixed SNAPSHOT with build timestamp 20071002.124230-6
> 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.
