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

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