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 2013/02/27 15:13:13 UTC

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

    [ https://issues.apache.org/jira/browse/FELIX-3651?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13588368#comment-13588368 ] 

Felix Meschberger edited comment on FELIX-3651 at 2/27/13 2:12 PM:
-------------------------------------------------------------------

Targeted PID is described in Configuration Admin V 1.5 and required to be supported in Extenders (See 104.3.3 in the Enterprise spec).

I think we should restrict this issue to handling Configuration Admin 1.4 location binding and treated Configuration Admin 1.5 targeted PIDs in a separate issue. WDYT ?
                
      was (Author: fmeschbe):
    Targeted PID is not related to location binding. This issue is about hanlding Configuration.getBundleLocation properly.

Targeted PID as described in Configuration Admin V 1.5 and required to be supported in Extenders (See 104.3.3 in the Enterprise spec). I think this is important enough to be treated in a separate issue. WDYT ?
                  
> 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