I tried using the log component (log:category?level=...) however it only
displayed the object identifier and no information on the body or the
header.
I'll check out the debugger another time, it looks like a good start. For
now, I've resorted to using a quick bean route using a simple class like
this:
public static class LogBean
{
public void doSomething(@Headers Map<String,Object> headers, @Body
String body) {
log.debug("headers=>"+headers);
}
}
BTW, I am using commons-logging with log4j. I don't know if this affects the
output of the log component.
Cheers!
Seon Lee
James.Strachan wrote:
>
> I often modify a route like this...
>
> from(...)
> to("log:Foo").
> to(...);
>
>
> to add an extra
>
> from(...)
> to("log:Foo").
> to(...);
>
> route to add more logging. Or turn debug logging high. Or sometimes
> when things are wacky I add a custom processor...
>
>
> from(...)
> process(new Processor() {
> public void process(Exchange) {
> // set a break point here!
> }
> ).
> to(...);
>
> So I can easily set a breakpoint and look at the exchange / message /
> headers / body etc.
>
> We need to make this a bit simpler though!
>
> FWIW I've an experimental debugger framework...
> http://activemq.apache.org/camel/debugger.html
>
> which can be enabled which then adds an interceptor which can record
> the exchanges passed into each step of a route and can trace them etc.
> Its kinda early days and could use some love; but its a kinda start
> along the road to having a better framework for diagnosing things
> going wrong mid-route etc.
>
> --
> James
> -------
> http://macstrac.blogspot.com/
>
> Open Source Integration
> http://open.iona.com
>
>
--
View this message in context:
http://www.nabble.com/Is-there-a-WIKI-page-describing-class-type-returned-by-getBody%28%29-method---tp16677652s22882p17870016.html
Sent from the Camel - Users mailing list archive at Nabble.com.
