[
https://issues.apache.org/activemq/browse/CAMEL-818?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jonathan Anstey updated CAMEL-818:
----------------------------------
Attachment: preserveExchangeTypeInRoutingSlip.patch
Patch to fix the issue.
The fix employs a technique similar to that of the pipeline processor to
preserve the exchange type. Basically, in order for a type of Exchange to be
propagated, it must override the newInstance method so the routing slip has a
way to create a clean instance of it.
> Should preserve the exchange type in the routing slip
> -----------------------------------------------------
>
> Key: CAMEL-818
> URL: https://issues.apache.org/activemq/browse/CAMEL-818
> Project: Apache Camel
> Issue Type: Bug
> Components: camel-core
> Affects Versions: 1.3.0, 1.4.0
> Reporter: Jonathan Anstey
> Fix For: 1.5.0
>
> Attachments: preserveExchangeTypeInRoutingSlip.patch
>
>
> Currently, the routing slip will create a new InOut exchange for each target
> based on the target endpoint type. This means that someone calling from a jbi
> endpoint (or other endpoint with custom exchange) into the routing slip will
> have their exchange type changed (to mostly likely DefaultExchange). I will
> be including a patch to fix this issue shortly.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
