James,
We could also look at it from the interceptor end and improve that so it
knows where it is being invoked in the route. For example: if the
interceptor knows about the previous/next step in the route is, it can
also log other messages based on where in the route it is (or omit
logging for some steps).
Regards,
Gert
James Strachan wrote:
Btw, isn't it possible to do the same thing with an interceptor?
Yeah you could do the same thing with an interceptor - I was just
thinking that you'd maybe want a specific logging message each time
its used. I guess an analogy is, I was pondering about whats the Camel
DSL equivalent of shoving in a LOG.info("foo") inside any line of a
route definition - which doesn't affect the flow at all. You can use
the tracer or add an interceptor to always log each step; but
sometimes you just wanna insert custom messages at specific points.
