You are viewing a plain text version of this content. The canonical link for it is here.
Posted to c-dev@axis.apache.org by ax...@ws.apache.org on 2004/09/21 13:51:37 UTC

[jira] Commented: (AXISCPP-158) XSD_BOOLEAN type is missing from the SOAPDeserialiser

The following comment has been added to this issue:

     Author: Fred Preston
    Created: Tue, 21 Sep 2004 4:51 AM
       Body:
Hi All,
According to the XML Schema definition (part 2).  The lexical definition of a boolean is 'An instance of a datatype that is defined as boolean can have the following legal literal values {true, false, 1, 0}'.  Thus the XSD_BOOLEAN deserialiser switch in SOAPDeserialiser.cpp now has to cope with diferent types of values.  To accomodate this change, the macro has had to be expanded.

Regards,

Fred Preston.
---------------------------------------------------------------------
View this comment:
  http://issues.apache.org/jira/browse/AXISCPP-158?page=comments#action_53277

---------------------------------------------------------------------
View the issue:
  http://issues.apache.org/jira/browse/AXISCPP-158

Here is an overview of the issue:
---------------------------------------------------------------------
        Key: AXISCPP-158
    Summary: XSD_BOOLEAN type is missing from the SOAPDeserialiser
       Type: Bug

     Status: Closed
   Priority: Major
 Resolution: FIXED

    Project: Axis-C++
 Components: 
             Serialization/Deserialization

   Assignee: Fred Preston
   Reporter: Fred Preston

    Created: Tue, 14 Sep 2004 8:17 AM
    Updated: Tue, 21 Sep 2004 4:51 AM
Environment: n/a

Description:
Problem:
When deserialising complex array type boolean, the array was always returning null.  The reason for this is because when deserialising a complex type (SoapDeSerializer.cpp), the type XSD_BOOLEAN is not been looked for in the switch that decodes either DOC or RPC encoded messages.

Solution:
By adding 'case XSD_BOOLEAN:' to the cases that deal with other integer types (i.e XSD_LONG and XSD_INTEGER), the type will then be parsed and the array should be filled with the correct values.


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