[ https://issues.apache.org/activemq/browse/CAMEL-1356?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Claus Ibsen updated CAMEL-1356: ------------------------------- Priority: Major (was: Critical) Fix Version/s: 1.6.1 2.0.0 Roman please also change the header key to the new CamelCase syntax for the 2.x commit. You can look at samples on the Exchange interface in 2.0. > 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, 1.6.1 > > > 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.