camel-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Andreas Siepert <>
Subject camel-test-blueprint regression related to property-placeholders with 2.15.3
Date Tue, 10 Nov 2015 18:57:06 GMT

i think there is a regression since version 2.15.3.

To reproduce the regression i changed the test
from the component camel-test-blueprint a bit, respectively the context

I added the trace Attribute to the camelContext
<camelContext xmlns=""

and added also the property to the etc/stuff.cfg

Until 2.15.2 this worked fine. From 2.15.3 on the property cannot be
replaced any more.

The loading of properties (ConfigAdmin) seemed to have been processed
before the camel context was created .in the old version of
CamelBlueprintTestSupport - now the order is switched somehow.

Another issue can be reproduced when replacing a property's String type
with int in the MyCoolBean class and setting its value by using the
placeholder like before but with an int value of course. The test run shows
that the placeholder ${..} will not be replaced and leads to a

I could not find a hint on changes in testing, so any help is appreciated
to make the tests run again. The production code that is under test works
fine in the karaf.


  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message