You need to set up the out message body instead of in message body. -- Willem Jiang
Red Hat, Inc. Web: http://www.redhat.com Blog: http://willemjiang.blogspot.com (English) http://jnn.iteye.com (Chinese) Twitter: willemjiang Weibo: 姜宁willem On July 27, 2014 at 12:52:08 AM, bocamel ([email protected]) wrote: > Thanks Claus! > > I tried a Processor, but the same error occurred. I do not know whether the > fact that this is on an OnException path made any difference. What I am > trying to do is to replace the soap fault from a web services server > (CxfPayload) with some meaningful response message (a string). > > Like I said in my original post, I do have a workaround - > type="String" /> > before I try to replace the fault message in the processor. > It is just not very elegant. > > Thanks again for your help! > > > > -- > View this message in context: > http://camel.465427.n5.nabble.com/setBody-Object-body-Class-T-type-does-not-seem-to-set-the-body-type-tp5754307p5754475.html > > Sent from the Camel - Users mailing list archive at Nabble.com. >
