Bad characters in complex type when set to null

— adrian.p.smith@bt.com wrote:

> OK.
>
> 1. I've edited the CH020XSoapPort.cpp file as suggested and, to stop the offending <pck> being
> returned, I have omitted it from the input. This seems to have highlighted a further issue. When
> a complexType is sent in the request, if all the elements are left un-initialized, the SOAP
> payload has some wierd characters in the first element of the complex type. Output from YATT
> shows this:
>
> <?xml version='1.0' encoding='utf-8' ?><SOAP-ENV:Envelope
> xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/"
> xmlns:xsd="http://www.w3.org/2001/XMLSchema"
> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"><SOAP-ENV:Body><ns1:getCustomerProfile
> xmlns:ns1="http://www.bt.com/css/mmbi/CH020X/"><mmbiInput xsi:type="ns2:mmbiInput"
> xmlns:ns2="http://www.bt.com/css/mmbi/2002/06/types"><correlId
> xsi:type="xsd:string">°G1</correlId><trace xsi:nil="true"/><location
> xsi:nil="true"/></mmbiInput><E2E xsi:type="ns2:E2E"
> xmlns:ns2="http://www.bt.com/css/mmbi/2002/06/types"><pck
> xsi:type="xsd:string">°G1</pck><callerId xsi:nil="true"/></E2E><telNr
>
xsi:type="xsd:string">01208561489</telNr></ns1:getCustomerProfile></SOAP-ENV:Body></SOAP-ENV:Envelope>
>
> notice the °G1 in <correlId> and <pck>. Subsequent elements in the complexType are correctly
> sent as xsi:nil="true". This causes a servlet error on the server side that results in a
> SOAP:Fault being returned, so we don't get to check out the de-serialisation. Is this another
> bug?
>

The WSDL from this issue is in Axis CPP 192