camel-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Claus Ibsen <>
Subject Re: Intercept a processor?
Date Tue, 12 Jan 2010 17:04:40 GMT
On Tue, Jan 12, 2010 at 5:56 PM, Johan Haleby <> wrote:
> Hi,
> I'm configuring routes using the Java DSL and it works very well. However
> during testing I'd like to somehow hook into the end of an already defined
> route to add notification support. The reason is that in my test I'm
> creating a message and pass it to a queue using Camel and this message is
> handled by a processor. After this processor has finished executing I'd like
> to receive some sort of notification but only during testing. The reason is
> that I'd like my test to wait until the processor has finished executing in
> my test case so that I can verify the result of the processor. For example:
> public void test() {
>  1. send a message to queue // just as you would in production
>  2. wait for the processor to finish // this is where I'd like to get a
> notification that the processor has finished so that it's ok to continue to
> the next step
>  3. verify result
> }
> The route may look something like:
> from("jms:queue:myqueue).process(new MyProcessor()); // A simplification of
> the production route
> Is there a preferred way of doing this in Camel without changing the code
> making up the "production route"? Or is there a better way to achieve it?

Chapter 6 in the book go over this issue and how to address that: (will be updated in next MEAP due this

However we made it easier to do nice and easy from an unit test in 2.2
which I assume is not the version of Camel you are using.
In 2.2 you can advice and route by adding additional cross cutting
concerns such as onCompletion, interceptors etc. which you would then
be able to use to know when its done.

In Camel 2.1 you got the EventNotification which you actually can use
for that to get notified when an Exchange is done as it emits a
I am currently improving that for 2.2 to let you filter out of the box
the notifier so you only receive interesting events. But that should
not hold you back from using that in 2.1.

We may improve this situation even more to make it easy as it can get
for testing production routes with test methods. So kinda inject mocks
at end of routes etc. so you can use that to verify behavior etc.

> /Johan
> --
> View this message in context:
> Sent from the Camel - Users mailing list archive at

Claus Ibsen
Apache Camel Committer

Author of Camel in Action:
Open Source Integration:

View raw message