If you change the data format of the cxf endpoint, you can not just redirect the input stream to a http endpoint, as the PAYLOAD message doesn’t has the soap envelope.
-- 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 April 21, 2015 at 12:42:41 PM, ercan.canlier ([email protected]) wrote: > Hello, > I have proxied real web service by defining proxy. I am tracing messages via > camel's tracer and writing to database and after that presenting on the web > application. The XML Request and Responses are quite long and i wanted to > make them smaller by setting dataFormat=PAYLOAD at CXF endpoint but when i > change this dataFormat=MESSAGE to dataFormat=PAYLOAD, i got this exception : > HTTP operation failed invoking http://localhost:9082/webservices/payment > with statusCode: 500 > What is wrong with the configuration? Could you please help? > Here is my endpoint configuration: > > > > address="http://localhost:${proxy.port}/gadget-ws-proxy/webservices/payment"; > endpointName="s:PaymentEndpoint" serviceName="s:PaymentEndpointService" > wsdlURL="etc/wsdl/report_incident.wsdl" xmlns:s="http://gadget.com"; /> > > > init-method="start" destroy-method="stop"> > > > value="http://localhost:${real.port}/webservices/payment"; /> > > > > > > uri="http://localhost:${real.port}/webservices/payment"; /> > > > > > > > > > > > > > > > Thanks in advance. > Best regards. > Ercan > > > > -- > View this message in context: > http://camel.465427.n5.nabble.com/HTTP-operation-failed-invoking-statusCode-500-tp5766085.html > > Sent from the Camel - Users mailing list archive at Nabble.com. >
