[FELIX-5684] Set multi-location for created configurations

• Type: Improvement
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Affects Version/s: fileinstall-3.5.4
• Fix Version/s: fileinstall-3.6.2
• Component/s: File Install
• Assignee: Guillaume Nodet
• Reporter: Grzegorz Grzybek
• Created: 29/Aug/17 07:35
• Updated: 06/Dec/17 15:59
• Resolved: 08/Sep/17 07:26

Description

By default, when fileinstall creates CM configurations, they have no locations set. According to spec:

104.4.2 Dynamic Binding:
A null location parameter can be used to create Configuration objects that are not yet bound.
In this case, the Configuration becomes bound to a specific location the first time that it is
compared to a Bundle’s location.

It is recommended that management agents explicitly set the location to a ? (a multi-location)
to allow multiple bundles to share PIDs and not use the dynamic binding facility.

I'd prefer "principle of least surprise", so CM configs created from etc/*.cfg files have multi-location is set by default (alternatively - we could have configuration option), so if for example there are two blueprint bundles using <cm:property-placeholder> for same PID, they can use the configuration without problems

Issue Links

• is related to: KARAF-2792 shared cm-properties empty for second bundle
• is related to: KARAF-5323 Set multi-location for created configurations
• supercedes: FELIX-4694 Support binding configuration to all registrations with the corresponding PID