On 15/04/2008, cmoulliard <[EMAIL PROTECTED]> wrote: > > Great idea. We should raise a JIRA to track this; it would be handy > information to know. > > > >> Are you going to open a JIRA task ? > > > We should make it easy to diagnose what the body type is; maybe we > should hack the log endpoint to make it easy to log the body content > and type? > http://activemq.apache.org/camel/log.html > > > >> According to this approach, the user is required to modify its CamelRoute > >> by adding : > .to("log:loggingCategory?level=DEBUG") > I thinkh that this appraoch is a little bit invasive. > It should be better to have a static Trace method defined at the level of > the CamelContext that we can activate or desactivate in the configure() > method in order to produce INFO, ERROR or DEBUG information and of course > generate the required information like the Body class type returned, headers > info, ... ?
Great idea! :) I guess there's a few different things we could trace... * all the exchange properties * all the message properties * the message headers * the message body type * the message body I wonder if we should always just log all of it; or have a few levels/categories of debug/trace logging so folks can do a less noisy log? -- James ------- http://macstrac.blogspot.com/ Open Source Integration http://open.iona.com
