New behaviour with ExchangePattern?

We use currently Camel 2.17.7 and will upgrade to 2.20.2. With 2.20.2 we have a new unexpected behaviour. We use in some routes ExchangePattern.InOnly. To remove unwanted headers, we set our required headers and body to Exchange.OUT. In the next bean we always get the "cleaned" exchange object

Apache CAmel to IMB MQ - JMSDestination

Hello, Issue: I am routing a message from active mq topic to Ibm mq queue, using Apache camel as the medium between these two. Apache camel is used for intermediate routing and for transformations. I am setting JMSDestination in message header as some topic name(eg: FMP/1.0/a/bguxmb). But when

Re: New behaviour with ExchangePattern?

Hi The new behaviour is the correct one - message transformation via setBody, transform, bean etc should be the same. On Tue, Mar 13, 2018 at 12:43 PM, Landl Hubert wrote: > We use currently Camel 2.17.7 and will upgrade to 2.20.2. > > With 2.20.2 we have a new