You should also look into your architecture to see why you need to share
some config. In some cases you
can extract the commonalities into a service that can then be regularly
configured by config admin.
Can you explain a bit what kind of configuration you need to share
between bundles?
Christian
On 25.09.2015 12:33, Arnaud Deprez wrote:
Hi,
@JP: The problem is not using 2 property placeholder, but sharing one
property placeholder across multiple bundles. And in that case, it
seems that we have to avoid it because it can cause trouble to the
Config Admin due to concurrency issues (it's actually what I read, I
didn't take a look to the code).
@Christian: Thanks for your answer. I actually had the same idea but
I'm a guy who is looking for icing by using Config Admin with its
dynamical behavior :-). But if there is no other solution, I'll go to
that direction.
On Fri, Sep 25, 2015 at 11:34 AM Christian Schneider
<[email protected] <mailto:[email protected]>> wrote:
You can use the <ext:property-placeholder placeholder-prefix="$["
placeholder-suffix="]"/>
It allows access to the System.properties and use it for shared
config.
See:
https://github.com/apache/karaf/blob/karaf-3.0.x/bundle/core/src/main/resources/OSGI-INF/blueprint/blueprint.xml
It can be used together with a cm:property-placeholder that
contains bundle specific config from config admin.
One problem is that the System properties do not support updates
in case of changes. So you can only use it for relatively fixed
configs.
Christian
--
Christian Schneider
http://www.liquid-reality.de
Open Source Architect
http://www.talend.com
