camel-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jonathan Anstey (JIRA)" <j...@apache.org>
Subject [jira] Resolved: (CAMEL-1122) Camel should propagate exception cause in InOnly scenarios
Date Wed, 26 Nov 2008 13:07:05 GMT

     [ 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.


Mime
View raw message