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] Resolved: (AXISCPP-145) Deserializer fails to deal with a sequence with a single element
Date Tue, 31 Aug 2004 05:53:20 GMT
Message:

   The following issue has been resolved as FIXED.

   Resolver: Samisa Abeysinghe
       Date: Mon, 30 Aug 2004 10:52 PM

Found a problem in SoapDeSerializer::getCmplxArray document style related code and fixed it.
Now it seems to work fine.
---------------------------------------------------------------------
View the issue:
  http://issues.apache.org/jira/browse/AXISCPP-145

Here is an overview of the issue:
---------------------------------------------------------------------
        Key: AXISCPP-145
    Summary: Deserializer fails to deal with a sequence with a single element
       Type: Bug

     Status: Resolved
   Priority: Major
 Resolution: FIXED

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

   Assignee: Samisa Abeysinghe
   Reporter: Samisa Abeysinghe

    Created: Mon, 30 Aug 2004 6:25 PM
    Updated: Mon, 30 Aug 2004 10:52 PM
Environment: All platforms

Description:
The deserializer tries to pull a second element from the stream wehn only one elemnt of an
unbounded sequence is available.

e.g.
For inquire_v2.wsdl get_businessDetail method; I get the following in the response SOAP message.

<discoveryURLs>
<discoveryURL useType="businessEntity">
http://www-3.ibm.com/services/uddi/testregistry/uddiget?businessKey=D368F080-8423-11D6-9FFC-000C0E00ACDD
</discoveryURL>
</discoveryURLs>

corrsponding to the xsd
<xsd:element name="discoveryURLs" type="uddi:discoveryURLs"/>
        <xsd:complexType name="discoveryURLs">
                <xsd:sequence>
                        <xsd:element ref="uddi:discoveryURL" maxOccurs="unbounded"/>
                </xsd:sequence>
        </xsd:complexType>

While deserializing, the program correctly identifies the first discovery URL, however, it
tries to read a second discovery URL without realizing there is only one available, and hence
fails.



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