[CAMEL-9313] CamelBlueprintTestSupport - can't initialize ConfigAdmin configurations

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 2.15.4
• Fix Version/s: 2.15.6, 2.16.2, 2.17.0
• Component/s: camel-blueprint
• Estimated Complexity: Unknown
• Assignee: Grzegorz Grzybek
• Reporter: Andreas Siepert
• Created: 12/Nov/15 08:13
• Updated: 19/Dec/19 17:30
• Resolved: 12/Dec/15 19:40

Description

The bugfix CAMEL-8948 seems to make older timing problems related to property-placeholders visible.

To reproduce the problem i changed the test
org.apache.camel.test.blueprint.ConfigAdminNoReloadLoadConfigurationFileTest
from the component camel-test-blueprint a bit, respectively the context
"org/apache/camel/test/blueprint/configadmin-no-reload-loadfile.xml":

I added the trace Attribute to the camelContext:

<camelContext xmlns="http://camel.apache.org/schema/blueprint" trace="{{tracing}}"> 

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

tracing=true 

Until 2.15.2 this worked fine. From 2.15.3 on the property cannot be
replaced any more.
But, if setting a breakpoint in CamelBlueprintTestSupport#createBundleContext at loadConfigAdminConfigurationFile() (Line 123 in 2.15.4) - the error occurs even in older versions like 2.14 - so the timing problem seems to be there for a while but did not occur because the loading of the configAdminFile seems to be faster than the event handling during service registration triggered by the code some lines above.

The issue can also 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
NumberfFormatException.

The production code that is under test works fine in karaf.

Issue Links

• is duplicated by: CAMEL-9377 [test-blueprint] support configadmin as source of initial properties for BP camel context
• is related to: CAMEL-8122 camel:run using <useBlueprint> option does not launch camel example project
• is related to: CAMEL-9636 CamelBlueprintTestSupport - initialization error in case of empty cm:property-placeholder
• is related to: CAMEL-10476 configAdminFile not used to populate property placeholders in camel-test-blueprint when run via camel-maven-plugin