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/03/19 11:12:32 UTC

[jira] Commented: (FELIX-258) Support Configuration Admin configuration

    [ https://issues.apache.org/jira/browse/FELIX-258?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12482049 ] 

Felix Meschberger commented on FELIX-258:
-----------------------------------------

One thing I forgot: This patch uses ConfigurationAdmin.getConfiguration(String pid) to retrieve the configuration of a component. This is very easy to implement but has the disadvantage that ConfigurationPlugins will not be called. The reason for this have been elaborated upon in the Mailing List but may be summarized as follows:

ConfigurationPlugins are only called when the configuration is provided to a ManagedService[Factory] through one of the update methods. These methods are called in a separate thread. So timing is somewhat difficult to manage when activating a component which gets configuration asynchronously.

I think, if ConfigurationPlugins become an issue, we can still implement it then.

> Support Configuration Admin configuration
> -----------------------------------------
>
>                 Key: FELIX-258
>                 URL: https://issues.apache.org/jira/browse/FELIX-258
>             Project: Felix
>          Issue Type: Improvement
>          Components: Declarative Services
>            Reporter: Felix Meschberger
>         Attachments: FELIX-258.diff
>
>
> 112.6, Component Properties, and 112.7, Deployment, state that the Configuration Admin service must be queried for configuration properties to provide to the ComponentContext.
> I will attach a patch, which provides this integration.

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