[
http://issues.apache.org/jira/browse/AXISCPP-802?page=comments#action_12331770
]
nadir amra commented on AXISCPP-802:
------------------------------------
Manohar,
Can you redo test? This is now hopefully fixed. Combination of fixing the
client tests so that the following defines are used when defining long long
values to be used in test cases:
#ifdef WIN32
#define LONGLONGVALUE(value) value##I64
#define UNSIGNED_LONGLONGVALUE(value) value##UI64
#else
#define LONGLONGVALUE(value) value##LL
#define UNSIGNED_LONGLONGVALUE(value) value##ULL
#endif
in conjunction with the update to
NonNegativeInteger::deserializeNonNegativeInteger() so that it now performs the
deserialization instead of calling Integer class to do the deserialization.
> wrong output for maxInclusive value in XSD_unsignedLong type
> ------------------------------------------------------------
>
> Key: AXISCPP-802
> URL: http://issues.apache.org/jira/browse/AXISCPP-802
> Project: Axis-C++
> Type: Bug
> Components: XSD Types
> Versions: current (nightly)
> Reporter: Manohar
> Assignee: nadir amra
>
> According to the XSD specification, when maxInclusive value
> 18446744073709551615 is given as an input it is serialize/deserialized to a
> wrong value 384. The output should be same as input given but it's different
> in this case.
> XSD_unsignedLongClient.cpp test shows this problem.
> 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
