felix-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Felix Meschberger (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (FELIX-3377) Allow a component to update its own service properties
Date Sat, 05 May 2012 17:37:50 GMT

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

Felix Meschberger updated FELIX-3377:

    Attachment: FELIX-3377-returnDictionary.patch

Here is my proposal.

Instead of extending the ActivatorParameter this patch introduces a MethodResult conveying
the result.

In addition a new namespace .../scr/v1.2.0-felix is introduced. The component must be declared
with this namespace for the return functionality to be available.
> Allow a component to update its own service properties
> ------------------------------------------------------
>                 Key: FELIX-3377
>                 URL: https://issues.apache.org/jira/browse/FELIX-3377
>             Project: Felix
>          Issue Type: Improvement
>          Components: Declarative Services (SCR)
>    Affects Versions:  scr-1.6.0
>            Reporter: David Jencks
>         Attachments: FELIX-3377-2.diff, FELIX-3377-3.diff, FELIX-3377-4.diff, FELIX-3377-returnDictionary.patch,
> If you just register a service in code, you can give the ServiceRegistration to the service
and it can update its service properties to reflect what it can discover about its environment.
 This proposes that services registered through DS should be able to do this too, by calling
an updateProperties(Dictionary) method on the ComponentContext.  (Since we'd need a spec update
to add the method to ComponentContext, I added a new interface that ComponentContextImpl implements).
> Right now a service could get Config Admin and modify the properties there, but then
(a) the update method is called even though the component itself initiated the changes and
(b) the new property values are persisted which is presumably not desired.
> According to the spec config admin properties override default property values specified
in the component xml.  I think that in order to reduce confusion, once a property has been
set through config admin it should not be possible to update it through this update method.
 This also makes implementing this idea easy.
> IIUC this idea does not make sense for component factories.
> This idea was originally suggested by Erin Schnabel in OSGI bug 2250.

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira


View raw message