Yeah, I think the better solution could be we can let the CamelBlueprintTestSupport support to create the context per test class. I will work on it today.
-- Willem Jiang Red Hat, Inc. FuseSource is now part of Red Hat Web: http://www.fusesource.com | http://www.redhat.com Blog: http://willemjiang.blogspot.com (http://willemjiang.blogspot.com/) (English) http://jnn.iteye.com (http://jnn.javaeye.com/) (Chinese) Twitter: willemjiang Weibo: 姜宁willem On Tuesday, March 26, 2013 at 10:42 PM, milanmilas wrote: > Similar issue with CamelBlueprintTestSupport. > Resolution: > > > public class RouteTest extends CamelBlueprintTestSupport { > private static int num = 8567; > @Override > protected String getBlueprintDescriptor() { > ++num; > return "/OSGI-INF/blueprint/blueprint.xml"; > } > > @Override > protected Properties useOverridePropertiesWithPropertiesComponent() { > Properties extra = new Properties(); > extra.put("service.address", "http://localhost:"+(num)); > return extra; > } > --------------------------------------------------------------------------------- > <cm:property-placeholder persistent-id="my-placeholders"> > <cm:default-properties> > <cm:property name="service.address" value="" /> > </cm:default-properties> > </cm:property-placeholder> > > <cxf:cxfEndpoint id="routerEndpoint" > address="{{service.address}}/CxfMtomRouterPayloadModeTest/jaxws-mtom/hello" > > > > -- > View this message in context: > http://camel.465427.n5.nabble.com/My-camel-CXF-tests-fails-if-they-run-together-tp696559p5729852.html > Sent from the Camel - Users mailing list archive at Nabble.com > (http://Nabble.com).
