[
https://issues.apache.org/activemq/browse/CAMEL-1233?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=48536#action_48536
]
Claus Ibsen commented on CAMEL-1233:
------------------------------------
Fixed in trunk
Sending
camel-core/src/main/java/org/apache/camel/util/ExchangeHelper.java
Sending
camel-core/src/test/java/org/apache/camel/processor/MultiCastAggregatorTest.java
Adding
camel-core/src/test/java/org/apache/camel/processor/PipelineMEPTest.java
Sending
camel-core/src/test/java/org/apache/camel/processor/PipelineTest.java
Sending
camel-core/src/test/java/org/apache/camel/processor/SplitterTest.java
Adding
camel-core/src/test/java/org/apache/camel/processor/onexception/InterceptAlterMessageBeforeRedeliveryTest.java
Transmitting file data ......
Committed revision 732378.
> Pipeline could change the MEP unintended
> ----------------------------------------
>
> Key: CAMEL-1233
> URL: https://issues.apache.org/activemq/browse/CAMEL-1233
> Project: Apache Camel
> Issue Type: Bug
> Components: camel-core
> Affects Versions: 1.5.0
> Reporter: Claus Ibsen
> Assignee: Claus Ibsen
> Priority: Critical
> Fix For: 2.0.0
>
> Attachments: CAMEL-1233.patch
>
>
> 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.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
