Thanks hekonsek for the reply. I'll do it as soon as I can (I need to cleanup the code from all references to my company).
I think the problem is on how the new Camel handles the command: exchange.getIn().setBody(null) where: - exchange is DefaultExchange - exchange.getIn() is GenericFileMessage With Camel 2.9.3 the value of exchange.getIn().getBody() would is Null after the command above. With Camel 2.15.2 the value of exchange.getIn().getBody() is an instance of java.io.File with: filePath = null path = "C:\input_file.txt" prefixLength = 3 status = null Has anybody noticed this behaviour? -- View this message in context: http://camel.465427.n5.nabble.com/Exchange-setBody-not-working-with-Camel-2-15-2-tp5767420p5767473.html Sent from the Camel - Users mailing list archive at Nabble.com.
