You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@camel.apache.org by "Jonathan Anstey (JIRA)" <ji...@apache.org> on 2008/11/26 12:23:05 UTC

[jira] Created: (CAMEL-1122) Camel should propagate exception cause in InOnly scenarios

Camel should propagate exception cause in InOnly scenarios
----------------------------------------------------------

                 Key: CAMEL-1122
                 URL: https://issues.apache.org/activemq/browse/CAMEL-1122
             Project: Apache Camel
          Issue Type: Bug
    Affects Versions: 1.5.0
            Reporter: Jonathan Anstey
            Assignee: Jonathan Anstey
             Fix For: 1.5.1, 2.0.0


In the case an exception is handled by the DeadLetterChannel, Camel will currently set the exception to null and add an exchange property containing the exception. We should also add this as a message header so that it will be propagated to external services, like a JBI service.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

[jira] Resolved: (CAMEL-1122) Camel should propagate exception cause in InOnly scenarios

Posted by "Jonathan Anstey (JIRA)" <ji...@apache.org>.

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

Jonathan Anstey resolved CAMEL-1122.
------------------------------------

    Resolution: Fixed

Fixed on trunk and 1.x

> Camel should propagate exception cause in InOnly scenarios
> ----------------------------------------------------------
>
>                 Key: CAMEL-1122
>                 URL: https://issues.apache.org/activemq/browse/CAMEL-1122
>             Project: Apache Camel
>          Issue Type: Bug
>    Affects Versions: 1.5.0
>            Reporter: Jonathan Anstey
>            Assignee: Jonathan Anstey
>             Fix For: 1.5.1, 2.0.0
>
>
> In the case an exception is handled by the DeadLetterChannel, Camel will currently set the exception to null and add an exchange property containing the exception. We should also add this as a message header so that it will be propagated to external services, like a JBI service.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.