If your processor is doing something like below, the only thing I can
think of is PAYLOAD mode was not specified properly. You can raise the
log level to DEBUG or TRACE to see what is going on.
public void process(final Exchange exchange)throws Exception {
...
CxfPayload<SoapHeader> responsePayload =new
CxfPayload<SoapHeader>(null, outElements);
exchange.getOut().setBody(responsePayload);
}
On 03/20/2011 12:59 PM, Claus Ibsen wrote:
On Sun, Mar 20, 2011 at 1:55 PM, hyjshanghai<[email protected]> wrote:
I have a camel route like this (I removed the< and> symbols to prevent from
being filtered by Nabble):
route
from uri="cxf:bean:dummySerivceEndpoint" /
process ref="endProcessor" /
/route
As is shown above, dummySerivceEndpoint is simply an entrance to accept SOAP
messages. It is synchronous, and uses the PAYLOAD message format.
End processor invokes exchange.getOut().setBody(cxfPayload) to manually set
the response to be returned to the client, where cxfPayload's body contains
a W3C XML DOM object built from a file on the local disk.
To use the route, I send a SOAP message to dummySerivceEndpoint with the XML
sender plug-in of the Eclipse IDE.
However, despite that exchange.out is set by endProcessor, I still get a
SOAP message with empty SOAP body in the "Response text" control of the XML
Sender. Why?
Read this FAQ
http://camel.apache.org/using-getin-or-getout-methods-on-exchange.html
And post your code you do in the processor
--
View this message in context:
http://camel.465427.n5.nabble.com/How-to-Get-SOAP-Response-from-the-Last-Camel-Processor-in-the-Route-tp4127850p4135591.html
Sent from the Camel - Users mailing list archive at Nabble.com.
