226.7. 模拟现有端点
可作为 Camel 2.7 提供
Camel 现在允许您自动模拟 Camel 路由中的现有端点。
注意
它的工作原理是 端点仍然在操作中。另一种情况是,注入 Mock 端点并接收消息,然后将消息委派给目标端点。您可以将此操作视为截获类型,并委派或端点监听程序。
假设您有以下给定的路由:
Route(路由)
@Override
protected RouteBuilder createRouteBuilder() throws Exception {
return new RouteBuilder() {
@Override
public void configure() throws Exception {
from("direct:start").to("direct:foo").to("log:foo").to("mock:result");
from("direct:foo").transform(constant("Bye World"));
}
};
}
然后,您可以使用 Camel 中的 建议 带功能来模拟来自单元测试给定路由中的所有端点,如下所示:
提供模拟所有端点的建议
public void testAdvisedMockEndpoints() throws Exception {
// advice the first route using the inlined AdviceWith route builder
// which has extended capabilities than the regular route builder
context.getRouteDefinitions().get(0).adviceWith(context, new AdviceWithRouteBuilder() {
@Override
public void configure() throws Exception {
// mock all endpoints
mockEndpoints();
}
});
getMockEndpoint("mock:direct:start").expectedBodiesReceived("Hello World");
getMockEndpoint("mock:direct:foo").expectedBodiesReceived("Hello World");
getMockEndpoint("mock:log:foo").expectedBodiesReceived("Bye World");
getMockEndpoint("mock:result").expectedBodiesReceived("Bye World");
template.sendBody("direct:start", "Hello World");
assertMockEndpointsSatisfied();
// additional test to ensure correct endpoints in registry
assertNotNull(context.hasEndpoint("direct:start"));
assertNotNull(context.hasEndpoint("direct:foo"));
assertNotNull(context.hasEndpoint("log:foo"));
assertNotNull(context.hasEndpoint("mock:result"));
// all the endpoints was mocked
assertNotNull(context.hasEndpoint("mock:direct:start"));
assertNotNull(context.hasEndpoint("mock:direct:foo"));
assertNotNull(context.hasEndpoint("mock:log:foo"));
}
请注意,模拟端点被赋予了 URI Vulnerability:& lt;endpoint>,如 模拟:direct:foo。INFO 级别的 Camel 日志是模拟的端点:
INFO Adviced endpoint [direct://foo] with mock endpoint [mock:direct:foo]
注意
模拟端点不使用参数
端点,模拟它们的参数会被剥离。例如,端点 log:foo?showAll=true 将模拟到以下端点 模拟:log:foo。请注意,参数已被删除。
它还可能仅使用模式模拟某些端点。例如,模拟您 执行 的所有日志端点,如下所示:
提供只使用模式的模拟日志端点 的建议
public void testAdvisedMockEndpointsWithPattern() throws Exception {
// advice the first route using the inlined AdviceWith route builder
// which has extended capabilities than the regular route builder
context.getRouteDefinitions().get(0).adviceWith(context, new AdviceWithRouteBuilder() {
@Override
public void configure() throws Exception {
// mock only log endpoints
mockEndpoints("log*");
}
});
// now we can refer to log:foo as a mock and set our expectations
getMockEndpoint("mock:log:foo").expectedBodiesReceived("Bye World");
getMockEndpoint("mock:result").expectedBodiesReceived("Bye World");
template.sendBody("direct:start", "Hello World");
assertMockEndpointsSatisfied();
// additional test to ensure correct endpoints in registry
assertNotNull(context.hasEndpoint("direct:start"));
assertNotNull(context.hasEndpoint("direct:foo"));
assertNotNull(context.hasEndpoint("log:foo"));
assertNotNull(context.hasEndpoint("mock:result"));
// only the log:foo endpoint was mocked
assertNotNull(context.hasEndpoint("mock:log:foo"));
assertNull(context.hasEndpoint("mock:direct:start"));
assertNull(context.hasEndpoint("mock:direct:foo"));
}
支持的模式可以是通配符或正则表达式。有关此问题的详细信息,请参阅 Intercept,及其与 Camel 使用的相同匹配功能。
注意
模拟端点时会导致在消息到达模拟时复制消息。
这意味着 Camel 将使用更多内存。当您在很多消息中发送时,可能不适用。