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 "Adrian Dick (JIRA)" <ax...@ws.apache.org> on 2005/09/19 15:17:28 UTC
[jira] Closed: (AXISCPP-780) Serialize/Deserialize problem with XSD_negativeInteger type
[ http://issues.apache.org/jira/browse/AXISCPP-780?page=all ]
Adrian Dick closed AXISCPP-780:
-------------------------------
Resolution: Duplicate
> Serialize/Deserialize problem with XSD_negativeInteger type
> -----------------------------------------------------------
>
> Key: AXISCPP-780
> URL: http://issues.apache.org/jira/browse/AXISCPP-780
> Project: Axis-C++
> Type: Bug
> Components: XSD Types
> Versions: current (nightly)
> Reporter: Manohar
>
> Hi,
> When the maxInclusive value (which is "-1") for xsd_negativeInteger is given as an input it is serialized/deserialized to some other value and resulted as 18446744073709551615 number . And the same happens when other negative inputs like -2 or -3 are given. The specification says that the ·value space· of negativeInteger is the infinite set {...,-2,-1}.
> Here is the piece of code which demonstrates the problem.
> sprintf(endpoint, "%s", url);
> XSD_negativeInteger* ws = new XSD_negativeInteger(endpoint);
> try
> {
> result = ws->asNonNillableElement((xsd__negativeInteger)-1);
> cout << "non-nillable element=" << result << endl;
> }
> catch(AxisException& e)
> {
> cout << "AxisException : " << e.what() << endl;
> }
> In the process of serialization/deserialization the minus sign '-' is removed and the value isge chand to 18446744073709551615.
> I think this not the correct behaviour. Any comments ?
> I will add a test case for this problem soon.
> Regards
> Manohar
--
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
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira