axis-c-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From axis-c-...@ws.apache.org
Subject [jira] Closed: (AXISCPP-193) Bad characters in complex type when set to null
Date Tue, 12 Oct 2004 15:37:51 GMT
Message:

   The following issue has been closed.

   Resolver: Mark Whitlock
       Date: Tue, 12 Oct 2004 8:37 AM

I have now fixed this problem by getting WSDL2WS to initialise all
fields of all complex types in their constructor.
---------------------------------------------------------------------
View the issue:
  http://issues.apache.org/jira/browse/AXISCPP-193

Here is an overview of the issue:
---------------------------------------------------------------------
        Key: AXISCPP-193
    Summary: Bad characters in complex type when set to null
       Type: Bug

     Status: Closed
   Priority: Major
 Resolution: FIXED

    Project: Axis-C++
 Components: 
             Serialization/Deserialization
   Fix Fors:
             1.3 Final
   Versions:
             1.3 Final

   Assignee: Mark Whitlock
   Reporter: John Hawkins

    Created: Thu, 7 Oct 2004 3:10 AM
    Updated: Tue, 12 Oct 2004 8:37 AM

Description:

--- 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


---------------------------------------------------------------------
JIRA INFORMATION:
This message is automatically generated by JIRA.

If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa

If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira


Mime
View raw message