You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@felix.apache.org by "David Jencks (JIRA)" <ji...@apache.org> on 2012/05/12 01:39:50 UTC

[jira] [Updated] (FELIX-3506) SCR bind/unbind/update methods should be able to return a map of service properties like the activate/deactivate/modified methods.s

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

David Jencks updated FELIX-3506:
--------------------------------

    Attachment: FELIX-3506.diff

extend the "return a map of service properties" functionality to bind/unbind/update methods, with a test.
                
> SCR bind/unbind/update methods should be able to return a map of service properties like the activate/deactivate/modified methods.s
> -----------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: FELIX-3506
>                 URL: https://issues.apache.org/jira/browse/FELIX-3506
>             Project: Felix
>          Issue Type: Improvement
>          Components: Declarative Services (SCR)
>    Affects Versions:  scr-1.6.0
>            Reporter: David Jencks
>            Assignee: Felix Meschberger
>         Attachments: FELIX-3506.diff
>
>
> cf FELIX-3377.
> The point of this feature is to let a component respond to changes in its environment by changing its service properties.  One of the obvious environment changes is for a dynamic service to be bound or unbound while the component is active.  Therefore we should extend the "return a map" style to the bind/unbind/updated method.
> A simple use case I thought of....  suppose you have a service with unsecured functionality and secured functionality and an optional dynamic reference to a security service.  It could use the bind and unbind methods for the security service to indicate in its own service properties how much functionality was available.

--
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