There doesn't appear to be support for nullable values. In the generated
SoapObject subclasses, in initWithNode, values are blindly converted to numeric
values discarding the "null" state, like this:
self.MyDoubleField = [[Soap getNodeValue: node withName: @"MyDoubleField"]
doubleValue];
In this case, a double property will be returned as 0.0 regardless of if the
node value (a string) is null or "0.0".
Null has a specific meaning in some cases and can be different from the meaning
of zero. The generated code discards that information.
Original issue reported on code.google.com by sebastie...@macadamian.com on 26 Sep 2011 at 7:53
Original issue reported on code.google.com by
sebastie...@macadamian.com
on 26 Sep 2011 at 7:53