Page History

...

See Try Catch Finally

Using Interceptors

You can register interceptors on a RouteBuilder so that they are inherited by all child routes. You can also use the DSL itself to write interceptors...

// lets log all steps in all routes
intercept().to("log:foo").proceed();

from("seda:foo").to("seda:bar");

You can also add a predicate to the intercept() method so that your interceptor will only be invoked if the predicate is true.

// lets log messages from gold customers
intercept(xpath("/customer[@type='gold']").to("log:customer").proceed();

from("seda:foo").to("seda:bar");

Changes in Camel 1.4

In Camel 1.4 proceed() is now default, so the examples above can be written as:

// lets log all steps in all routes
intercept().to("log:foo");

from("seda:foo").to("seda:bar");

Proceed means that Camel will continue the normal route path after the interception. All the examples shown is logging examples where the routing is supposed to continue by its normal path. Camel is so powerful that you can also use interceptors to alter the route path and change the cause of action.
The example below will intercept all exchanges that has an istest flag set to true and move the exchange to a test queue. We append the stop() to indicate that the interceptor should not proceed - thus any istest message is intercepted and does not route in the normal route path, but is moved to the test queue.

...

See Intercept

See Also

For more examples of the DSL in action see

...