[
https://issues.apache.org/activemq/browse/CAMEL-1356?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Roman Kalukiewicz closed CAMEL-1356.
------------------------------------
Resolution: Fixed
Fix Version/s: (was: 1.6.1)
Used exchange property to store the exception. Property name is
Exchange.EXCEPTION_CAUGHT constant.
Committed only to 2.0.0 as it completely changes the behavior of exception
handling. If someone had code depending on "caught.exception" header it will
break.
> TryProcessor sets "caught.exception" header to in message, while there can be
> out already
> -----------------------------------------------------------------------------------------
>
> Key: CAMEL-1356
> URL: https://issues.apache.org/activemq/browse/CAMEL-1356
> Project: Apache Camel
> Issue Type: Bug
> Components: camel-core
> Affects Versions: 1.6.0
> Reporter: Roman Kalukiewicz
> Assignee: Roman Kalukiewicz
> Fix For: 2.0.0
>
>
> Error exists in
> {{org.apache.camel.processor.TryProcessor.handleException(Exchange,
> Throwable)}}. If your exchange has already out message (that can happen if
> you set out and then throw an exception. Then the exception caught is set on
> in message. When it reaches a pipeline it will be lost after first hop.
> I believe {{TryProcessor}} should do what Pipelient does - copy *out* to *in*
> in new exchange if out exists.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
