[
https://issues.apache.org/jira/browse/CAMEL-8017?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14203913#comment-14203913
]
Ankit Thakkar commented on CAMEL-8017:
--------------------------------------
These parameters are already added to custom exchange formatter,
showAll=false, showBody=false, showCaughtException=true, showStackTrace=true
However, LogComponent calls DefaultComponent method while creating log endpoint,
if (!endpoint.isLenientProperties())
{ validateParameters(uri, parameters, null); }
This check is failing with custom formatter. optionPrefix for method
validateParameters always passed as null. Below check getting failed.
if (param.size() > 0) {
throw new ResolveEndpointFailedException(uri, "There are " +
param.size()
+ " 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=[" + param + "]");
}
> 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)
