[SMXCOMP-494] Camel route should avoid returning null out message when receiving InOut exchange

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Affects Version/s: servicemix-camel-2009.01
• Fix Version/s: servicemix-camel-2009.02
• Component/s: servicemix-camel
• Assignee: Gert Vanthienen
• Reporter: Gert Vanthienen
• Created: 30/Mar/09 19:01
• Updated: 31/Mar/09 13:03
• Resolved: 31/Mar/09 13:03

Description

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.