Thanks for the fix James, and for the explanation RomKal. It was the EL implementation indeed, we use EL in most of our routes. But it's working again now.
Arjan James.Strachan wrote: > > This was a gremlin in the EL implementation; it was forcing an empty > output message to be created which was then being used as the next > output in the pipeline; if no OUT message is created in a pipeline, > the input is passed to the next step. (Another work around would be to > use setOutBody()). > > I've fixed this now and added a minor refactored version of your test > in the camel-juel module (NullBodyTest) > -- View this message in context: http://www.nabble.com/setBody%28el%28-%29%29-creates-null-body-tf4805396s22882.html#a13788097 Sent from the Camel - Users mailing list archive at Nabble.com.
