camel-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Claus Ibsen (JIRA)" <>
Subject [jira] [Updated] (CAMEL-6466) Log component URI parameters should be able to override custom formatter properties
Date Mon, 02 Sep 2013 08:53:52 GMT


Claus Ibsen updated CAMEL-6466:

    Fix Version/s:     (was: 2.12.1)
> Log component URI parameters should be able to override custom formatter properties
> -----------------------------------------------------------------------------------
>                 Key: CAMEL-6466
>                 URL:
>             Project: Camel
>          Issue Type: Improvement
>          Components: camel-core
>    Affects Versions: 2.11.0
>            Reporter: Nathan Jensen
>            Assignee: Claus Ibsen
>            Priority: Minor
>             Fix For: 2.11.2, 2.12.0
> Our project uses a custom log formatter of type org.apache.camel.component.log.LogFormatter,
the only difference is we have changed the defaults from camel's standard defaults.  Unfortunately,
by registering a custom formatter we can no longer have a route specifically diverge from
the system wide formatter for special cases.
> For example, the following works when we don't have a custom formatter but fails when
do have a custom formatter:
> <touri="log:pluginName?level=ERROR&amp;showBody=false&amp;showCaughtException=true&amp;showStackTrace=true"/>
> It fails with a FailedToCreateRouteException with the message "There are 3 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=[{showBody=false, showCaughtException=true,
> The root of the problem is that the logic in LogComponent.createEndpoint() only sets
the URI parameters on the localFormatter if there is no custom formatter already registered,
otherwise it tries to set the parameters on the endpoint itself and not the formatter.
> It would be nice if the log route URIs were able to override parameters on the custom
formatter for routes that need special cases.

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see:

View raw message