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 2011/05/31 14:41:47 UTC

[jira] [Resolved] (FELIX-2960) Run Configuration Plugins

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

Felix Meschberger resolved FELIX-2960.
--------------------------------------

       Resolution: Won't Fix
    Fix Version/s:     (was: scr-1.6.2)

BJ Hargrave says: "ConfigurationPlugins was just a bad idea."

Thus, we should not implement this here are and assume that either configuration plugins will be removed altogether or API will be provided to get at configuration having passed configuration plugins. In any case, DS does not have to do anything right now.

> Run Configuration Plugins
> -------------------------
>
>                 Key: FELIX-2960
>                 URL: https://issues.apache.org/jira/browse/FELIX-2960
>             Project: Felix
>          Issue Type: Improvement
>          Components: Declarative Services (SCR)
>    Affects Versions:  scr-1.6.0
>            Reporter: Felix Meschberger
>            Assignee: Felix Meschberger
>
> In earler releases configuration has been provided to components by registering ManagedService[Factory] services on behalf of the components.
> This has been changed by directly getting required configuration from the Configuration Admin Service. This change causes the Configuration Plugins to not be called any longer before providing configuraiton to the components.
> I would assume the specification intent is for the component to be provided configuration as if ManagedService[Factory] services would be registered for them. This means, that Configuration Plugins must actually be called by the Declarative Services Runtime in this case.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira