[jira] [Resolved] (CAMEL-4080) Propagate caused exception in DeadLetterChannel error handler

["Claus Ibsen (JIRA)" <ji...@apache.org>]

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

Claus Ibsen resolved CAMEL-4080.
--------------------------------

       Resolution: Cannot Reproduce
    Fix Version/s:     (was: 2.9.0)

DLC already propagate exception.

> Propagate caused exception in DeadLetterChannel error handler
> -------------------------------------------------------------
>
>                 Key: CAMEL-4080
>                 URL: https://issues.apache.org/jira/browse/CAMEL-4080
>             Project: Camel
>          Issue Type: Improvement
>          Components: camel-core
>    Affects Versions: 2.7.1
>            Reporter: Claus Ibsen
>            Assignee: Claus Ibsen
>            Priority: Minor
>             Fix For: 2.8.0
>
>
> We should preserve the EXCEPTION_CAUGHT exchange property on the DLC when the message is error handler by it. End users would like to be able to see whats the caused exception and maybe do some custom processing.
> Of course they can use an onException for that as well. But I guess the DLC should support that out of the box as well. Since its stored on the exchange property it wont affect the Message instance. (body and headers).
> See nabble
> http://camel.465427.n5.nabble.com/Splitter-StopOnException-doesn-t-forward-the-exception-on-the-Exchange-tp4469882p4469882.html

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira