[
https://issues.apache.org/jira/browse/FELIX-5303?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15369836#comment-15369836
]
David Jencks commented on FELIX-5303:
-------------------------------------
Well, as discussed in the osgi issue and as must be obvious after a little
consideration, there's no way for DS to set the location without causing bugs.
Furthermore since at least R5 the management agent is strongly recommended to
set the bundle location to either a specific bundle or a multi-location;
dynamic binding is pretty much deprecated, so with an up to date management
agent you wouldn't have been able to tell if a configuration was used from it's
non-null bundle location anyway.
> Configurations don't get bound to component bundle
> --------------------------------------------------
>
> Key: FELIX-5303
> URL: https://issues.apache.org/jira/browse/FELIX-5303
> Project: Felix
> Issue Type: Bug
> Components: Declarative Services (SCR)
> Affects Versions: scr-2.0.4
> Reporter: Carsten Ziegeler
> Fix For: scr-2.0.6
>
>
> It seems that configurations do not get bound to the bundle of the component.
> The component is using optional as the configuration policy and the the
> configuration is not using a targetted PID.
> This works:
> - create configuration for PID A
> - install bundle B with a component using PID A
> - above component gets reactivated with configuration
> - configuration is not bound to bundle B, bundleLocation is still null
> In 2.0.0 and 2.0.2 the configuration got bound to the component bundle, so it
> seems to be a deviation.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
