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 2013/02/27 07:08:16 UTC

[jira] [Assigned] (FELIX-3651) Properly support configuration location binding

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

David Jencks reassigned FELIX-3651:
-----------------------------------

    Assignee: David Jencks  (was: Felix Meschberger)
    
> Properly support configuration location binding
> -----------------------------------------------
>
>                 Key: FELIX-3651
>                 URL: https://issues.apache.org/jira/browse/FELIX-3651
>             Project: Felix
>          Issue Type: Improvement
>          Components: Declarative Services (SCR), Specification compliance
>    Affects Versions:  scr-1.6.0
>            Reporter: Felix Meschberger
>            Assignee: David Jencks
>
> Currently the location binding support is based on an older Configuration Admin specification and always mandates the configuration location to exactly match the bundle location of the component to provide with the location.
> This strict matching has been released in Configuration Admin 1.4 to allow for so-called multi-target locations starting with a '?' character. Such bindings are ignored if security is disabled and allows for "region" matching if security is enabled using a permission check on the bound location instead of comparing the target services bundle location.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira