Andrew,
To wire up the proxy route to transform your request and response you have
two choices:
Synchronously
from WS
transformRequestProcessor
to HTTP
transformResponseProcessor
The route ends at transformResponseProcessor which should set the Exchange
Out message to your response XML.
o
@Willem: Fair enough, then. I think it would be good if it was stated
explicitly that the body is used as-is with no encoding, as I obviously
found it confusing.
@Scott: Undecided. Happy to use either POJO or PAYLOAD for CXF, whichever
ends up being easier (probably PAYLOAD). And yes, there is a w
Hi Andrew,
Regarding the second part of your question, do you use CXF to deserialize
the request Object?
Also, is there a web service response expected after the HTTP4 POST is
processed?
On Thu, May 31, 2012 at 4:54 AM, Willem Jiang wrote:
> Camel-HTTP4 components just takes the message body as
Camel-HTTP4 components just takes the message body as an input stream, if
you want to do the encoding you can add a processor or dataformat to do
this kind of work.
Willem
On Thu, May 31, 2012 at 4:34 PM, Andrew Thorburn wrote:
> When sending a message to an HTTP4 Endpoint, will the content of
When sending a message to an HTTP4 Endpoint, will the content of the
message body be automatically encoded? e.g. The spaces replaced with %20
and whatever else is necessary to ensure that the POST request isn't
mangled on the other side.
I can't see anything in the documentation to tell me whether
