此内容没有您所选择的语言版本。
Chapter 10. System Management
Abstract
The system management patterns describe how to monitor, test, and administer a messaging system.
10.1. Detour 复制链接链接已复制到粘贴板!
复制链接链接已复制到粘贴板!
Detour 复制链接链接已复制到粘贴板!
复制链接链接已复制到粘贴板!
The Detour from the Introducing Enterprise Integration Patterns allows you to send messages through additional steps if a control condition is met. It can be useful for turning on extra validation, testing, debugging code when needed.
Example 复制链接链接已复制到粘贴板!
复制链接链接已复制到粘贴板!
In this example we essentially have a route like
from("direct:start").to("mock:result") with a conditional detour to the mock:detour endpoint in the middle of the route..
from("direct:start").choice()
.when().method("controlBean", "isDetour").to("mock:detour").end()
.to("mock:result");
from("direct:start").choice()
.when().method("controlBean", "isDetour").to("mock:detour").end()
.to("mock:result");
Using the Spring XML Extensions
whether the detour is turned on or off is decided by the
ControlBean. So, when the detour is on the message is routed to mock:detour and then mock:result. When the detour is off, the message is routed to mock:result.
For full details, check the example source here: