You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@camel.apache.org by "Willem Jiang (JIRA)" <ji...@apache.org> on 2014/12/09 06:47:13 UTC

[jira] [Assigned] (CAMEL-8091) DefaultExchangeFormatter does not consider Exchange.LOG_DEBUG_BODY_MAX_CHARS

     [ https://issues.apache.org/jira/browse/CAMEL-8091?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Willem Jiang reassigned CAMEL-8091:
-----------------------------------

    Assignee: Willem Jiang

> DefaultExchangeFormatter does not consider Exchange.LOG_DEBUG_BODY_MAX_CHARS
> ----------------------------------------------------------------------------
>
>                 Key: CAMEL-8091
>                 URL: https://issues.apache.org/jira/browse/CAMEL-8091
>             Project: Camel
>          Issue Type: Improvement
>          Components: camel-core
>    Affects Versions: 2.13.3, 2.14.0
>            Reporter: Stephan Siano
>            Assignee: Willem Jiang
>         Attachments: 0001-CAMEL-8091-DefaultExchangeFormatter-does-not-conside.patch
>
>
> The DefaultExchangeFormatter does not consider the Exchange.LOG_DEBUG_BODY_MAX_CHARS context property that is supposed to limit the size of the logged payload.
> It is possible to set a maxChars on the DefaultExchangeFormatter, but that has a different semantics (limits the length of the formatted exchange, not of the message payload) and is complicated to set in some cases (e.g. in the case of the default error handler)
> The attached extension also honors the Exchange.LOG_DEBUG_BODY_MAX_CHARS context property when formatting the exchange.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)