骆驼NotifyBuilder总是返回false [英] Camel NotifyBuilder always returns false

问题描述

我有一条相当简单的路线:

I've got a fairly simple route:

PerfStubRouteBuilder.java

public class PerfStubRouteBuilder extends SpringRouteBuilder {

    /* (non-Javadoc)
     * @see org.apache.camel.builder.RouteBuilder#configure()
     */
    @Override
    public void configure() throws Exception {
        from("direct:test-aces-input")
        .log("Creating test Accident Number header")
        .setHeader("AccidentNumber", simple("AB999999999"))
        .log("Test Accident Number header created : ${header.AccidentNumber}")
        .end();
    }
}

我正在如下测试:

PerfStubRouteBuilderTest.java

public class PerfStubRouteBuilderTest extends CamelTestSupport {
    @Produce(uri = "direct:test-aces-input")
    ProducerTemplate template;

    PerfStubRouteBuilder route = new PerfStubRouteBuilder();
    Exchange exch = new DefaultExchange(context);

    @Override
    protected RouteBuilder createRouteBuilder() {
        return route;
    }

    @Test
    public void test_PerfStubRouteBuilder_happyPath_addsAccidentNumberHeaderToExchange() throws Exception {
        startCamelContext();
        NotifyBuilder notify = new NotifyBuilder(context).from("direct:test-aces-input").whenDone(1).filter(header("AccidentNumber").isEqualTo("AB999999999")).create();
        template.send(exch);
        assertTrue(notify.matches(10, TimeUnit.SECONDS));
        stopCamelContext();
    }
}

assertTrue总是返回为false，因此尽管目前不能确定，但​​我怀疑我没有正确使用NotifyBuilder.本质上，我想检查交换是否通过路由，并且将实际路由中指定的标头添加到交换中.我要发生的是，如果与该标头值组合的交换使它到达路由的末尾，则发生匹配，因此发生了过滤步骤.我想避免在路由的末尾添加端点，例如，通过AdviceWith鉴于路由本身是如此的小巧和简单，开始为此类次要测试添加模拟端点似乎有点繁重

assertTrue always come back as false, so I suspect I'm not using the NotifyBuilder correctly although at this point I can't be certain. Essentially I want to check that an exchange makes it through the route and the header specified in the actual route is added to the exchange. What I want to happen is for a match to occur if an exchange with that header value combo makes it to the end of the route, hence the filter step. I want to avoid adding an endpoint at the end of the route, for example, via AdviceWith given how small and simple the route itself is , it seems a bit heavyweight to start adding in mock endpoints for such a minor test

更新:

尝试从表达式中删除过滤器部分，将NotifyBuilder保留为NotifyBuilder notify = new NotifyBuilder(context).from("direct:test-aces-input").whenDone(1).create(); ，测试仍然失败

Tried removing the filter portion from the expression, leaving the NotifyBuilder as NotifyBuilder notify = new NotifyBuilder(context).from("direct:test-aces-input").whenDone(1).create(); , the test still fails

推荐答案

从测试中的端点创建交换，例如

Create the exchange from the endpoint in the test like

Endpoint endpoint = context.getEndpoint("direct:test-aces-input");
Exchange exchange = endpoint.createExchange();
template.send(exchange);

或直接使用sendBody

or just directly use sendBody

tempalte.sendBody("")

这篇关于骆驼NotifyBuilder总是返回false的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！