Hi Rico,
I'm using guththila rather than libxml2. The responses are constructed using the autogenerated classes from WSDL2CPP (part of the WSF/C++ packaging) rather than being hand-generated. Since this is just one client I was hoping for a solution that I could make client specific. When I previously went down the route of creating custom XML responses that the one client would accept, the rest of Axis wouldn't accept the responses - so no simple way of writing test suites. richard. On Fri, Feb 11, 2011 at 3:49 AM, Rico M <[email protected]> wrote: > Hi Richard, > > From what i see , its mostly additional name spaces and , removal of name > spaces in the soap body. The latter can be handled by modifying some core > variables. How is your soap body built ? I am using libxml2 to build the > soap body and do not encounter such name space problems. I am sure the > built-in parser has such control as well. > > Cheers! > > > On Fri, Feb 11, 2011 at 7:21 AM, Richard Offer <[email protected]>wrote: > >> >> Hi Damitha, >> >> >> The client is expecting. >> >> >> <soapenv:Envelope xmlns:soapenc=" >> http://schemas.xmlsoap.org/soap/encoding/"; xmlns:soapenv=" >> http://schemas.xmlsoap.org/soap/envelope/"; xmlns:xsd=" >> http://www.w3.org/2001/XMLSchema"; xmlns:xsi=" >> http://www.w3.org/2001/XMLSchema-instance";> >> <soapenv:Body> >> <MsgResponse xmlns="urn:msg"> >> <returnval xsi:type="MsgType" type="message">Message Text</returnval> >> </MsgResponse> >> </soapenv:Body> >> </soapenv:Envelope> >> >> >> >> Axis2/C is currently sending >> >> <soapenv:Envelope xmlns:soapenv=" >> http://schemas.xmlsoap.org/soap/envelope/";> >> <soapenv:Body> >> <n:MsgResponse xmlns:n="urn:msg"> >> <ns1:returnval xsi:type="MsgType" type="message">message >> Text</ns1:returnval> >> </n:MsgResponse> >> </soapenv:Body> >> </soapenv:Envelope> >> >> >> Thanks for any commnets. >> >> >> richard. >> >> >> >> >> On Wed, Feb 9, 2011 at 5:56 PM, Damitha Kumarage <[email protected]>wrote: >> >>> Hi Richard, >>> Can you show us the message that client expects and what you actually >>> receive from Axis2/C?. >>> Axis2/C architeture allows handlers only to manipulate soap headers. >>> Thanks, >>> Damitha >>> >>> Richard Offer wrote: >>> >>>> >>>> Hi, >>>> >>>> I'm developing a replacement axis2/c based web service that needs to >>>> inter-operate with an existing client. >>>> >>>> >>>> The client is expecting a specific response that I can't seem to get >>>> with Axis (my guess is that the client is using its own hand-coded XML >>>> parser rather than a toolkit, so it needs byte-for-byte compatible message >>>> with the existing service). >>>> >>>> >>>> I had tried to use a Apache Filter module, but that didn't seem to work. >>>> >>>> If I take the axis2 handler approach, is there a pointer to how to >>>> approach modifying the body content within a handler function ? >>>> >>>> >>>> Thanks, >>>> >>>> richard. >>>> >>>> >>> >>> -- >>> __________________________________________________________________ >>> >>> Damitha Kumarage >>> Technical Lead; WSO2 Inc. >>> "Oxygenating the Web Service Platform; " http://www.wso2.com/ >>> >>> blog: " http://damithakumarage.wordpress.com/ >>> __________________________________________________________________ >>> >>> --------------------------------------------------------------------- >>> To unsubscribe, e-mail: [email protected] >>> For additional commands, e-mail: [email protected] >>> >>> >> >
