OK - One other thing on this.
If you add some default properties elements in your blueprint, you’re test
works as written as well
<cm:property-placeholder
persistent-id="my.camel.bp"
update-strategy="reload">
<cm:default-properties>
<cm:property name="my.label" value="" />
<cm:property name="my.logger" value="" />
<cm:property name="my.flag" value="" />
<cm:property name="my.path" value="" />
</cm:default-properties>
</cm:property-placeholder>
> On Feb 19, 2016, at 3:57 PM, Ephemeris Lappis <ephemeris.lap...@gmail.com>
> wrote:
>
> Hello.
> Indeed, it seems to work with Camel 2.16.2. As I've explained in my previous
> reply, I've refactored the blueprints to extract in separated files the
> roots that have unresolved properties. This will allow us to test all the
> important blueprints with the targeted version of Camel.
> An explanation of what has been fixed about Camel life cycle with the 2.16.2
> should be welcome...
> Thanks to all.
> Regards.
>
>
>
> --
> View this message in context:
> http://camel.465427.n5.nabble.com/cxf-bean-doesn-t-resolve-properties-with-CamelBlueprintTestSupport-tp5777834p5777956.html
> Sent from the Camel - Users mailing list archive at Nabble.com.
