Camel supports three kinds of interceptors:
These interceptors supports the following features:
Intercept is like a regular interceptor that is applied on each processing step the Exchange undergo while its being routed. You can think of it as a AOP before that is applied at each DSL keyword you have defined in your route.
The classic Hello World example would be:
What happens is that the Exchange is intercepted before each processing step, that means that it will be intercepted before
So in this sample we intercept the Exchange twice.
The when predicate is also support on the intercept so we can attach a Predicate to only trigger the interception under certain conditions.
And in the route below we want to stop in certain conditions, when the message contains the word 'Hello':
The same hello world sample in Spring DSL would be:
And the sample for using the when predicate would be:
And the sample for using the when and stop would be:
InterceptFrom is for intercepting any incoming Exchange, in any route (it intercepts all the from DSLs). This allows you to do some custom behavior for received Exchanges. You can provide a specific uri for a given Endpoint then it only applies for that particular route.
So lets start with the logging example. We want to log all the incoming requests so we use interceptFrom to route to the Log component. As proceed is default then the Exchange will continue its route, and thus it will continue to mock:first.
You can also attach a Predicate to only trigger if certain conditions is meet. For instance in the route below we intercept when a test message is send to us, so we can do some custom processing before we continue routing:
And if we want to filter out certain messages we can use the stop() to instruct Camel to stop continue routing the Exchange:
And if want to only apply a specific endpoint, as the seda:bar endpoint in the sample below, we can do it like this:
Intercept is of course also available using Spring DSL as shown in the sample below:
Available as of Camel 2.0
Intercept send to endpoint is triggered when an Exchange is being sent to the intercepted endpoint. This allows you to route the Exchange to a Detour or do some custom processing before the Exchange is sent to the original intended destination. You can also skip sending to the intended destination. By default Camel will send to the original intended destination after the intercepted route completes. And as the regular intercept you can also define an when Predicate so we only intercept if the Predicate evaluates to true. This allows you do do a bit of filtering, to only intercept when certain criteria is meet.
Let start with a simple example, where we want to intercept when an Exchange is being sent to mock:foo:
And this time we add the Predicate so its only when the message body is Hello World we intercept.
And to skip sending to the mock:foo endpoint we use the *skip() DSL in the route at the end to instruct Camel to skip sending to the original intended endpoint.
Intercept endpoint is of course also available using Spring DSL.
We start with the first example from above in Spring DSL:
And the 3rd with the skip, notice skip is set with the skipSendToOriginalEndpoint attribute on the interceptSendToEndpoint tag:
The interceptFrom and interceptSendToEndpoint supports endpoint URI matching by the following rules in the given order:
The real endpoint that was intercepted is stored as uri in the message IN header with the key Exchange.INTERCEPTED_ENDPOINT.
Match by wildcard allows you to match a range of endpoint or all of a given type. For instance use uri="file:*" will match all File based endpoints.
Wildcards is match that the text before the * is matched against the given endpoint and if it also starts with the same characters its a match. For instance you can do:
To intercept any files received from the order/inbox folder.
Match by regular expression is just like match by wildcard but using regex instead. So if we want to intercept incoming messages from gold and silver JMS queues we can do: