Does your wsdl define a response message? If it doesn't, it is normal that you get an empty response. In that case, you see an empty HTTP 202 response with the current CXF but with older CXF versions, you will see an HTTP 200.
2012/12/14 brxv <[email protected]>: > Hello. > I'm just startig out with camel and am tryng to achieve the following > scenario. > > 1) start up a contract-first cxf service which accepts a message from a > consumer, say soapUI > 2) process the message and use it as an input to another web-service > 3) do some further fiddling with the message and then hand a valid response > back to the consumer. > > I've been trying to follow various examples and the guidance from "Camel In > Action" - which is very good but no matter what I seem to try, i'm getting > the same answer: > My service returns an http 200 to soapui, but won't fill in the response > body, even if i use > exchange.getIn.setBody.... > > i've tried simplifying the route so that it does as little as possible, but > no joy: > > the route is as follows (angle brackets omitted) > > > from uri=cxf:bean enrichFilesEndpoint > camel:process ref="processorbean" > > > > the endpoint is just a simple cxf bean (pointing to generated wsdtojava > artefacts), and the processor is just setting the output to a literal > string. > > any help very much appreciated > Al. > > > > > > > > > -- > View this message in context: > http://camel.465427.n5.nabble.com/Trouble-with-CXF-soap-response-tp5724105.html > Sent from the Camel - Users mailing list archive at Nabble.com.
