[
https://issues.apache.org/jira/browse/FELIX-3651?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13588621#comment-13588621
]
David Jencks commented on FELIX-3651:
-------------------------------------
IIUC the location binding bits are dealing with no location set, and
multi-locations of the form ?symbolic-name. DId I miss something here?
(location changed is definitely separate)
I don't have a strong opinion on how many issues we need, but I have one commit
that takes care of both the location binding and the targetedPID. I started
with the targetedPID and the location binding stuff is somewhat intertwined and
I don't think I can separate them easily.
> 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
