[CAMEL-1233] Pipeline could change the MEP unintended

• Type: Bug
• Status: Closed
• Priority: Critical
• Resolution: Fixed
• Affects Version/s: 1.5.0
• Fix Version/s: 1.6.0, 2.0-M1
• Component/s: camel-core
• Assignee: Claus Ibsen
• Reporter: Claus Ibsen
• Created: 07/Jan/09 13:26
• Updated: 31/Jul/09 06:33
• Resolved: 07/Jan/09 16:46

Description

When exchanges is processed from pipeline they result is copyed as input to the next exchange. However during this copy Camel could potentially change the MEP to InOut. It should respect the original MEP.

The flaw is in ExchangeHelper#copyResults

Fixing this also forces end users to use the correct send/request method on ProducerTemplate. Now Camel will keep the MEP.
So if you are using send then its inOnly and then you the there is no result. Use request for InOut MEP's.

This breaks a few of our own unit testing that was using the wrong method.