axis-c-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From John Hawkins <HAWKI...@uk.ibm.com>
Subject Re: [jira] Updated: (AXISCPP-371) Error deserializing empty arrays
Date Mon, 10 Jan 2005 10:07:29 GMT
Why don't we throw  an exception instead of returning -1 ? Isn't that the 
more OO way of doing it?



John Hawkins





"Unai Uribarri (JIRA)" <axis-c-dev@ws.apache.org> 
10/01/2005 09:46
Please respond to
"Apache AXIS C Developers List"


To
axis-c-dev@ws.apache.org
cc

Subject
[jira] Updated: (AXISCPP-371) Error deserializing empty arrays






     [ http://issues.apache.org/jira/browse/AXISCPP-371?page=history ]

Unai Uribarri updated AXISCPP-371:
----------------------------------

    Attachment: DeserializeEmptyArray.diff

I've modified getArraySize to return -1 on error, and fixed the array 
deserialization routines

> Error deserializing empty arrays
> --------------------------------
>
>          Key: AXISCPP-371
>          URL: http://issues.apache.org/jira/browse/AXISCPP-371
>      Project: Axis-C++
>         Type: Bug
>   Components: Serialization/Deserialization
>     Versions: 1.4 Final
>     Reporter: Unai Uribarri
>  Attachments: DeserializeEmptyArray.diff
>
> When the array length is 0, the deserialization routines fails.

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