[
https://issues.apache.org/jira/browse/FELIX-3651?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
David Jencks updated FELIX-3651:
--------------------------------
Description:
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.
In addition CA 1.5 introduces targeted PIDS. While these are not obviously
intertwined features the implementing code overlaps a bit.
was:
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.
Summary: Properly support configuration location binding and targeted
pids (was: Properly support configuration location binding)
> Properly support configuration location binding and targeted pids
> -----------------------------------------------------------------
>
> 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.
> In addition CA 1.5 introduces targeted PIDS. While these are not obviously
> intertwined features the implementing code overlaps a bit.
--
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
