You are viewing a plain text version of this content. The canonical link for it is here.
Posted to savan-dev@ws.apache.org by "Amila Chinthaka Suriarachchi (JIRA)" <ji...@apache.org> on 2010/05/09 07:04:50 UTC
[jira] Resolved: (AXIS2-3643) dateTime echo failes when input is
9999-12-31T23:59:59.9999999Z
[ https://issues.apache.org/jira/browse/AXIS2-3643?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Amila Chinthaka Suriarachchi resolved AXIS2-3643.
-------------------------------------------------
Resolution: Fixed
this has been fixed by changing the milisecond value to a long type. Problem does not occur at the trunk.
> dateTime echo failes when input is 9999-12-31T23:59:59.9999999Z
> ---------------------------------------------------------------
>
> Key: AXIS2-3643
> URL: https://issues.apache.org/jira/browse/AXIS2-3643
> Project: Axis2
> Issue Type: Bug
> Components: adb
> Reporter: Keith Godwin Chapman
> Assignee: Amila Chinthaka Suriarachchi
> Priority: Critical
>
> If date time is echoed and it is given the input 9999-12-31T23:59:59.9999999Z the response is 9999-12-31T23:59:59.141+00:00. Here the milliseconds are incorrect and it looks like this happens because of the follwoing logic in ConverterUtil at lines 973
> if (milliSecondPartLength != 3){
> // milisecond part represenst the fraction of the second so we have to
> // find the fraction and multiply it by 1000. So if milisecond part
> // has three digits nothing required
> miliSecond = miliSecond * 1000;
> for (int i = 0; i < milliSecondPartLength; i++) {
> miliSecond = miliSecond / 10;
> }
> }
> Here we multiply the milliseconds by 1000 and hence it overflows causing the problem.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: java-dev-unsubscribe@axis.apache.org
For additional commands, e-mail: java-dev-help@axis.apache.org