karaf-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Grzegorz Grzybek (JIRA)" <j...@apache.org>
Subject [jira] [Created] (KARAF-5323) Set multi-location for created configurations
Date Tue, 29 Aug 2017 07:36:00 GMT
Grzegorz Grzybek created KARAF-5323:

             Summary: Set multi-location for created configurations
                 Key: KARAF-5323
                 URL: https://issues.apache.org/jira/browse/KARAF-5323
             Project: Karaf
          Issue Type: Improvement
          Components: karaf-config
            Reporter: Grzegorz Grzybek

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
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

See FELIX-5684

This message was sent by Atlassian JIRA

View raw message