Re: CXF component attachment support for POJO not implemented as specified

Hi Willem, thank you. I have two comments: 1) It is used in three methods, one for producer and two for consumer. I believe it should be changed in all the methods so that it works in both directions. /populateExchangeFromCxfResponse(Exchange camelExchange, org.apache.cxf.message.Ex

CXF component attachment support for POJO not implemented as specified

Hi, the CXF description states: http://camel.apache.org/cxf.html#CXF-AttachmentSupport Attachment Support "/POJO Mode: Attachments are propagated to Camel message's attachments since 2.1. So, it is possible to retreive attachments by

Re: Must Processor check if Exchange has out message already?

OK, thank you. -- View this message in context: http://camel.465427.n5.nabble.com/Must-Processor-check-if-Exchange-has-out-message-already-tp5739977p5740139.html Sent from the Camel - Users mailing list archive at Nabble.com.

Re: Must Processor check if Exchange has out message already?

Hi Claus, thank you. I actually read this page. I was not just sure if the framework should guarantee that the out message is always null when I receive exchange in my processor because it is not the case when the binding component is used. -- View this message in context: http://camel.465427.

Must Processor check if Exchange has out message already?

Hi, until now I haven't checked Exchange.hasOut() in Processor.process(Exchange) and always used only Exchange.getIn(). However, I started using BindingComponent which creates BindingEndpoint and this BindingEndpoint calls delegate Processor with Exchange that has both in and out Messages set. M