camel-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Willem Jiang (JIRA)" <>
Subject [jira] [Commented] (CAMEL-5754) useOriginalMessage parameter of DefaultErrorHandler never be used
Date Mon, 29 Oct 2012 05:13:12 GMT


Willem Jiang commented on CAMEL-5754:

It's not a bug, as the defaultErrorHandler will not use the original message by default, and
it provides a way to let you set the option by using the DSL.
For the DeadLetterChannel, it needs to use the original message for store or processing.

Please drop an email to the user at if you are not sure about the usage of
API, so we can make things clear before filling a JIRA.
> useOriginalMessage parameter of DefaultErrorHandler never be used
> -----------------------------------------------------------------
>                 Key: CAMEL-5754
>                 URL:
>             Project: Camel
>          Issue Type: Bug
>          Components: camel-core
>    Affects Versions: 2.10.2
>         Environment: Camel 2.10.2 and old versions
>            Reporter: liugang
>            Assignee: Willem Jiang
>            Priority: Minor
> When declare a default error handle, the *useOriginalMessage* is configurable:
> {code}
> errorHandler(defaultErrorHandler().useOriginalMessage())
> {code}
> but is never be used, when creating *DefaultErrorHandler*, the passed parameter always
> {code}
>     public DefaultErrorHandler(CamelContext camelContext, Processor output, CamelLogger
logger, Processor redeliveryProcessor,
>             RedeliveryPolicy redeliveryPolicy, ExceptionPolicyStrategy exceptionPolicyStrategy,
Predicate retryWhile, ScheduledExecutorService executorService) {
>         super(camelContext, output, logger, redeliveryProcessor, redeliveryPolicy, null,
null, false, retryWhile, executorService);
>         setExceptionPolicy(exceptionPolicyStrategy);
>     }
> {code}
> but it works when using Dead letter queue.

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