[
https://issues.apache.org/activemq/browse/SMXCOMP-494?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gert Vanthienen resolved SMXCOMP-494.
-------------------------------------
Resolution: Fixed
Fixed in http://svn.eu.apache.org/viewvc?view=rev&revision=760421
> Camel route should avoid returning null out message when receiving InOut
> exchange
> ---------------------------------------------------------------------------------
>
> Key: SMXCOMP-494
> URL: https://issues.apache.org/activemq/browse/SMXCOMP-494
> Project: ServiceMix Components
> Issue Type: Bug
> Components: servicemix-camel
> Affects Versions: servicemix-camel-2009.01
> Reporter: Gert Vanthienen
> Assignee: Gert Vanthienen
> Fix For: servicemix-camel-2009.02
>
>
> When a Camel provider endpoint receives an InOut exchange, it depends on the
> Camel route to fill in the out message. Camel itself is far less strict in
> its MEP handling and it doesn't necessarily provide a value there. This will
> result in sending back the InOut exchange without an out NormalizedMessage,
> potentially confusing other endpoints.
> If no out message has been set, I think copying the resulting in message
> would make a sensible default. This is also what Camel itself does by
> default when an out-capable exchange doesn't have the out message set.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
