I don’t know if this fits your use case, but you could let Blueprint do the
substitution instead of camel.
<from uri=“cxf://bean:my.ws?…...loggingFeatureEnabled=${fv.soap.tracing}” />
> On Feb 18, 2016, at 4:30 AM, Ephemeris Lappis <ephemeris.lap...@gmail.com>
> wrote:
>
> Hello.
>
> I've a unit test class based on CamelBlueprintTestSupport that works as
> expected except if I let a "cxf:bean" route with a configuration property.
>
> The properties are loaded from a CFG file on the
> "loadConfigAdminConfigurationFile" call. They are all resolved as expected
> on any of all the routes components, exept with cxf:bean.
>
> The route endpoint is :
> **
>
> And the following exception is thrown :
> **
>
> In fact, the CXF route is not actually tested at this time (just the
> transformation, services call and processing routes are), and the class
> fails because of it.
>
> Any idea ?
>
> Thanks for your help.
>
> Regards.
>
>
>
> --
> View this message in context:
> http://camel.465427.n5.nabble.com/cxf-bean-doesn-t-resolve-properties-with-CamelBlueprintTestSupport-tp5777834.html
> Sent from the Camel - Users mailing list archive at Nabble.com.
