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/09/20 11:12:31 UTC
[jira] Created: (FELIX-374) Register ManagedService on behalf of
components to receive Configuration
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
Reporter: Felix Meschberger
Assignee: Felix Meschberger
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.
[jira] Resolved: (FELIX-374) Register ManagedService on behalf of
components to receive Configuration
Posted by "Felix Meschberger (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/FELIX-374?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Felix Meschberger resolved FELIX-374.
-------------------------------------
Resolution: Fixed
Fix Version/s: 1.0.0
The ImmediateComponentManager now registers as ManagedService (if not created on behalf of a ComponentFactory) to receive Configuration Admin configuration.
Fixed in Rev. 580883
> 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.
[jira] Updated: (FELIX-374) Register ManagedService on behalf of
components to receive Configuration
Posted by "Felix Meschberger (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/FELIX-374?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Felix Meschberger updated FELIX-374:
------------------------------------
Component/s: Declarative Services
Assign this issue to the Declarative Services component
> 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
>
> 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.
[jira] Closed: (FELIX-374) Register ManagedService on behalf of
components to receive Configuration
Posted by "Felix Meschberger (JIRA)" <ji...@apache.org>.
[ 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.
[jira] Updated: (FELIX-374) Register ManagedService on behalf of
components to receive Configuration
Posted by "Felix Meschberger (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/FELIX-374?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Felix Meschberger updated FELIX-374:
------------------------------------
Fix Version/s: (was: felix-1.0.0)
scr-1.0.0
> 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 (SCR)
> Reporter: Felix Meschberger
> Assignee: Felix Meschberger
> Fix For: scr-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.
[jira] Closed: (FELIX-374) Register ManagedService on behalf of
components to receive Configuration
Posted by "Felix Meschberger (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/FELIX-374?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Felix Meschberger closed FELIX-374.
-----------------------------------
Uploaded SNAPSHOT build number 20071001.145653-5 containing the fix.
Now closing this issue.
> 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.
[jira] Work started: (FELIX-374) Register ManagedService on behalf
of components to receive Configuration
Posted by "Felix Meschberger (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/FELIX-374?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Work on FELIX-374 started by Felix Meschberger.
> 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
>
> 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.
[jira] Reopened: (FELIX-374) Register ManagedService on behalf of
components to receive Configuration
Posted by "Felix Meschberger (JIRA)" <ji...@apache.org>.
[ 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.