Thanks for that link but I've been already through that FAQ many many times which didn't help me as well! It seems I'm too dummy to understand this API.
Yes I'm aware of the exchange.hasOut() semantics as well as the lazy instantiation of OUT through exchange.getOut() So again my question: - Do we currently have a Camel Producer behaving wrong concerning this question? - And still I think the fact that exchange.getOut() does lazily instantiate an OUT if OUT == null is an API flaw as this does bypass the semantics of the given exchange pattern of the exchange object. So that you can have an exchange with InOnly pattern having an OUT != null attached to it! Babak -- View this message in context: http://camel.465427.n5.nabble.com/About-what-to-do-with-the-Response-retrieved-through-a-Producer-when-the-Exchange-is-NOT-out-capable-tp5713946p5714015.html Sent from the Camel Development mailing list archive at Nabble.com.
