I don't understand why the OSGi configuration properties are resolved as
expected in this CXF route when deploying the bundle on ServiceMix, and are
not when testing it with the CamelBlueprintTestSupport.
In the same blueprint, I've other properties used in other Camel components
that are resolved in both cases. In the following example, the logger name
doesn't produce an error :
**
If I have understood well, when the CamelContext is set inside a blueprint
that comes with an OSGi property place holder, which is my case, no explicit
Camel place holder is needed. This is the way we've built many bundles for
many years with Camel and ServiceMix.
The OSGi configuration is declared with the associated persistence ID like
that :
**
And, this way, Camel properties are resolved whatever way we call them :
{{name}} in the blueprint, or in Simple or Groovy scripts too, using the
respective syntax.
So, I don't understand why the property in the CXF:BEAN endpoint's URI leads
to an exception, and only in the unit test.
Maybe something fails in the endpoint construction, perhaps because of some
missing package in the unit test path that is not logged in the console, and
produces a side effect ?
--
View this message in context:
http://camel.465427.n5.nabble.com/cxf-bean-doesn-t-resolve-properties-with-CamelBlueprintTestSupport-tp5777834p5777886.html
Sent from the Camel - Users mailing list archive at Nabble.com.
