Grzegorz Grzybek created FELIX-5684:
---------------------------------------
Summary: Set multi-location for created configurations
Key: FELIX-5684
URL: https://issues.apache.org/jira/browse/FELIX-5684
Project: Felix
Issue Type: Improvement
Components: File Install
Affects Versions: fileinstall-3.5.4
Reporter: Grzegorz Grzybek
Fix For: fileinstall-3.5.6
By default, when fileinstall creates CM configurations, they have no locations
set. According to spec:
{quote}
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.
{quote}
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
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
