[
https://issues.apache.org/jira/browse/FELIX-5303?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Carsten Ziegeler updated FELIX-5303:
------------------------------------
Summary: Configurations don't get bound to component bundle (was:
Configurations appearing after component is activated don't get bound)
> 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 that are created after a component has been
> activated are used but 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
> - configuration is bound to bundle B
> This does not seem to work
> - install bundle B with a component using PID A
> - as the component is using policy optional for a configuration, it gets
> activated
> - create configuration for PID A
> - above component gets reactivated with configuration
> - configuration is not bound to bundle B, bundleLocation is still null
> This worked in 2.0.2, so it seems to be a deviation.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
