Our use-case was in debugging why a processor was being triggered twice. We wanted to log immediately before the processor to see where the Exchange came from second time around.
I see a few people via Google asking how to log where the Exchange has been, thought something like this would be a useful quick tool in the toolbox. On 24 February 2016 at 10:35, Claus Ibsen <claus.ib...@gmail.com> wrote: > What kind of logging do you want. > > Do you mean that verbose logging you see when there is an exception? > > The message history on the exchange is stored as a list of events that > track the details. But the formatting is done elsewhere. > > > > On Wed, Feb 24, 2016 at 10:48 AM, James Green <james.mk.gr...@gmail.com> > wrote: > > Is this possible? > > > > We really just want to from().log("${exchange.history}").to() in our > route. > > Seems like this should be really easy? > > > > Thanks, > > > > James > > > > -- > Claus Ibsen > ----------------- > http://davsclaus.com @davsclaus > Camel in Action 2: https://www.manning.com/ibsen2 >