settings if they are
both set.
What do you think?
Best regards
Stephan
-Original Message-
From: Willem Jiang [mailto:willem.ji...@gmail.com]
Sent: Freitag, 28. November 2014 07:57
To: users@camel.apache.org
Subject: RE: Somewhat inconsistent behaviour for message logging
It is consistent
2014 06:28
To: users@camel.apache.org
Subject: Re: Somewhat inconsistent behaviour for message logging
We introduce a ExchangeFormatterRef option to RedeliveryErrorHandler[1] since
Camel
2.15.0, it should be more easy for us setup ExchangeFormatter for the
ErrorHandler
Hi,
I have looked into the coding for the logging of the payload in different
locations of the Camel coding, but it looks somewhat inconsistent to me.
In several places MessageHelper.extractBodyForLogging(Message) or
MessageHelper.extractBodyForLogging(Message, String) is used to get a payload
We introduce a ExchangeFormatterRef option to RedeliveryErrorHandler[1] since
Camel 2.15.0, it should be more easy for us setup ExchangeFormatter for the
ErrorHandler.
But It could more easy for us to manage the max chars option by set up the
properties through the camel context. Please feel
Stephan
-Original Message-
From: Willem Jiang [mailto:willem.ji...@gmail.com]
Sent: Freitag, 28. November 2014 06:28
To: users@camel.apache.org
Subject: Re: Somewhat inconsistent behaviour for message logging
We introduce a ExchangeFormatterRef option to RedeliveryErrorHandler[1] since
Camel
To: users@camel.apache.org
Subject: Re: Somewhat inconsistent behaviour for message logging
We introduce a ExchangeFormatterRef option to RedeliveryErrorHandler[1] since
Camel
2.15.0, it should be more easy for us setup ExchangeFormatter for the
ErrorHandler.
But It could more easy for us
