I just use one full copy of properties for tests and another that I include
in the bundle. If you don't put a camel context in the porperties then you
don't end up with multiple contexts and OSGi/karaf automatically pick up
all the blueprint files it finds in your OSGI-INF blueprint folders. So I
usually have a blueprint.xml that has the camel context and another one
with blueprint-properties.xml that only defines properties values but
doesn't have a camel context. The third test-blueprint-propertie.xml I
keep in src/test/resources and when I run CBTS I just do this:
private static final String TEST_BLUEPRINT_XML =
"test-blueprint-properties.xml,OSGI-INF/blueprint/blueprint.xml";
@Override
protected String getBlueprintDescriptor() {
return TEST_BLUEPRINT_XML;
}
On Fri, Feb 19, 2016 at 4:48 PM, Ephemeris Lappis <
ephemeris.lap...@gmail.com> wrote:
> Hello.
>
> Happy to see I'm not the only one getting such a problem !
>
> I've also modified the blueprints to put the entry routes that are
> configured with these problematical properties in a separted file that
> needs
> no real unit tests, and all the routes that are to be actually tested in
> other blueprints. As this leads to create multiple Camel contexts, routing
> is done with "vm" instead of "direct" from the head blueprint to others...
>
> Thanks for your feedback.
>
> Regards.
>
>
>
> --
> View this message in context:
> http://camel.465427.n5.nabble.com/cxf-bean-doesn-t-resolve-properties-with-CamelBlueprintTestSupport-tp5777834p5777955.html
> Sent from the Camel - Users mailing list archive at Nabble.com.
>
