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 <[email protected]> wrote: > 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 this is > handled automatically or whether I need to convert it myself. At this stage > it looks like it is handled automatically, since I don't see anything > telling me otherwise, but I'm not sure. > > More to the point, how do I pass multiple parameters as the body? e.g. I'd > like to have a Web Service call, transform whatever was passed to the web > service to parameters for an HTTP POST request, and pass them to the HTTP4 > endpoint. > > e.g. > > Given a Web Service Request, > > <soap:Body> > <request> > <p1>value1</p1> > <p2>value2&value2.1</p2> > </request> > </soap:Body> > > have the body of the POST request be: "p1=value1&p2=value2%26value2.1". My > request is a little more complex than that, but not by much. Hopefully what > I want makes sense? > > Thanks, > > - Andrew >
