I think it depends on what the WSDL says the input message type should be. For example, look at the WSDL fragment at the "For Step #4, replace..." section here: http://www.jroller.com/gmazza/entry/using_mtom_and_apache_fop
Glen Nick Cotter wrote: > > Hi, > > Should soap:body content be sent base64 encoded by default? > > I've been wiring up a web service client with CXF in Mule, in order to > send some quite ordinary XML: > > <HS_CreatePersonRequest> > <forenames>Frank</forenames> > <initials>S</initials> > <surname>Spencer</surname> > ...etc > </HS_CreatePersonRequest> > > - no images or raw binary data of any kind - and I'm seeing something > unexpected in the soap content I'm sending, namely that the body content > is base64 encoded: > > <soap:Body> > <HS_CreatePersonRequest > > xmlns="http://www.capita-software.co.uk/ABC/services/WSHsgCreatePerson/"; > xmlns:ns3="http://www.w3.org/2001/XMLSchema"; > xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"; > xsi:type="ns3:base64Binary"> > PD94bWwgdmVyc2lvbj0iMS4wIiBlbmNvZGluZz0iVVRGLTgiPz48SFNfQ3JlYXRlUGVyc29uUmVxdWVzdD48Zm9yZetc.... > etc... > </HS_CreatePersonRequest> > </soap:Body> > > I thought I'd see the XML in there, but I don't - the base64 code contains > the XML I'm expecting, so maybe this is ok. Is it? > > Kind regards > > Nick > -- View this message in context: http://www.nabble.com/soap%3Abody-content-is-base64-encoded---is-that-expected--tp23369457p23380510.html Sent from the cxf-user mailing list archive at Nabble.com.
