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

[jira] [Resolved] (CAMEL-8017) Custom ExchangeFormatter doesn't work for LogComponent

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

Claus Ibsen resolved CAMEL-8017.
--------------------------------
    Resolution: Invalid

Use the mailing list to get help first. 

Not sure how or what you do with an application restart. But you cannot just call context.stop and then context.start and then everything just works.



> Custom ExchangeFormatter doesn't work for LogComponent
> ------------------------------------------------------
>
>                 Key: CAMEL-8017
>                 URL: https://issues.apache.org/jira/browse/CAMEL-8017
>             Project: Camel
>          Issue Type: Bug
>          Components: camel-core
>    Affects Versions: 2.12.2
>         Environment: Production
>            Reporter: Ankit Thakkar
>
> Hello,
> We are using log: component to log request, response and exception details. We have been trying to customize DefaultExchangeFormatter to filter certain header fields getting logged in logger. 
> We have implemented custom ExchangeFormatter and registered in spring context with bean name 'logFormatter'. However, getting below exception during application service restart. 
> http://camel.apache.org/log.html#Log-Formatting
> Exception - 
> There are 4 parameters that couldn't be set on the endpoint. Check the uri if the parameters are spelt correctly and that they are properties of the endpoint. Unknown parameters=[{showAll=false, showBody=false, showCaughtException=true, showStackTrace=true}]
> The issue seems to be at this check in DefaultComponent,
>             if (!endpoint.isLenientProperties()) {
>                 validateParameters(uri, parameters, null);
>             }
> Please let me know if this issue can be fixed. 
> Thanks



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