@Jean-Baptiste We are using cm-properties as in the provided code before. I
don't see cm:properties in blueprint-cm-1.3.0.xsd
@Grzegorz we try to prepare the examples ASAP
śr., 13 lut 2019 o 18:39 Jean-Baptiste Onofré napisał(a):
> Hi,
>
> It's normal, and I bet it was the case before.
>
> Depe
Hi,
It's normal, and I bet it was the case before.
Depending how you create the config, it can be created empty (no
property first) and updated later.
You should use managed factory (so update reload in blueprint) to be up
to date.
I also notified it's especially true with cm:properties (instea
Do you have some extracted example (simple blueprint file) that can show
this problem? I'd be happy to track down this race condition...
regards
Grzegorz Grzybek
śr., 13 lut 2019 o 15:29 Dominik Przybysz napisał(a):
> We had this problem when we had only cm-properties, so we started to add
> pl
We had this problem when we had only cm-properties, so we started to add
placeholder. And it works fine in karaf 2.x and 4.0.4, but it doesn't work
in 4.2.2/3
śr., 13 lut 2019 o 15:18 Grzegorz Grzybek napisał(a):
> Hello
>
> Do you really need both? I vaguely remember that the race was with
> pr
Hello
Do you really need both? I vaguely remember that the race was with
property-placeholder, but not with cm-properties (or vice versa - sorry,
can't check now).
regards
Grzegorz Grzybek
śr., 13 lut 2019 o 14:57 Dominik Przybysz napisał(a):
> The problem is that we always have reloading for
The problem is that we always have reloading for the configuration in our
blueprint xmls and we always generate both cm-properties and
property-placeholder, e.g.
http://aries.apache.org/blueprint/xmlns/blueprint-cm/v1.2.0";
persistent-id="properties1" update-strategy="reload"/>
http://aries.apache
I think generally this can always happen.
I usually use update-strategy="reload" to make sure the new config is
applied.
See
https://github.com/cschneider/Karaf-Tutorial/blob/bf7c69efee2a49422106820a52e9a7ec24131bc3/configadmin/configapp-blueprint/src/main/resources/OSGI-INF/blueprint/context.xml
Hello
JBO - that's similar race we've observed (talked about this on IRC). I
remember we've found something (not synchronized, iterative copy of
properties between maps), but I can't remember the conclusion...
regards
Grzegorz Grzybek
śr., 13 lut 2019 o 14:11 Dominik Przybysz
napisał(a):
> Hi,
Hi,
we have a problem with Blueprint in newest Karaf versions. We try to
upgrade Karaf from version 4.0.4 to 4.2.2/4.2.3. As we do that, we have a
strange situation during application startup. Bundles await for Config
Admin startup (opinion based on logs), but after that, sometimes our CM
Propertie
