Camel
  1. Camel
  2. CAMEL-1233

Pipeline could change the MEP unintended

    Details

    • Type: Bug Bug
    • Status: Closed
    • Priority: Critical Critical
    • Resolution: Fixed
    • Affects Version/s: 1.5.0
    • Fix Version/s: 1.6.0, 2.0-M1
    • Component/s: camel-core
    • Labels:
      None

      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.

        Activity

        No work has yet been logged on this issue.

          People

          • Assignee:
            Claus Ibsen
            Reporter:
            Claus Ibsen
          • Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved:

              Development