Hi Rintcius
#1
I think the interceptor documentation is wrong. It is an all or nothing
strategy that if an exchange is intercepted it is not routed through the normal
route path. The interceptor wiki documentation is unfortunately wrong here as
it uses a step logging example.
I think that interceptors are used for snatching the exchange and diverting its
path to something else. Not for logging the steps.
#2
If you need the log every steps example I do think the trace() expression is a
step in that direction.
from("seda:a").trace("xxx").to("seda:b");
from("seda:b").trace("yyy").to("seda:c");
#3
I do think there should be a easy switch in Camel to turn on/off logging of the
steps into a logging category of your choice so you can use it for tracking
what is going on. I will raise a JIRA for this.
#4
I did not test the groovy as I was testing the code in camel-core where
camel-groovy is not a part of.
I will try the groovy case to see what is going on.
Med venlig hilsen
Claus Ibsen
......................................
Silverbullet
Skovsgårdsvænget 21
8362 Hørning
Tlf. +45 2962 7576
Web: www.silverbullet.dk
-----Original Message-----
From: Rintcius [mailto:[EMAIL PROTECTED]
Sent: 12. april 2008 11:08
To: [email protected]
Subject: Re: Some questions about a simple setHeader test
Thanks for looking at it, Claus.
Yes, I still have the same problem with interceptors. That is, what is
documented at http://activemq.apache.org/camel/dsl.html looks good (i.e.
usable) to me and that is what I meant to assert in the unit test. So I am
curious what you think is wrong about the interceptor documentation.
I don't have a real life use case yet, because I am still in evaluation
phase, but to mention an example, I thought it would be useful for
logging/debugging, to see what's happening at each step. So what I am seeing
in the unit test is not what I would expect, since it changes the delivery
of messages in ways that I cannot explain. (I expected camel interceptors to
act analogous to interceptors in AOP)
So are you saying that the groovy tests are running ok in your environment?
I can imagine that they are failing because of something in my environment
but I think it's weird that there's no stacktrace or error message. (Just
tried it again on HEAD after an update and they are still failing)
Rintcius
--
View this message in context:
http://www.nabble.com/Some-questions-about-a-simple-setHeader-test-tp16467528s22882p16647704.html
Sent from the Camel - Users mailing list archive at Nabble.com.
