You are viewing a plain text version of this content. The canonical link for it is here.
Posted to java-dev@axis.apache.org by "Lee Surprenant (JIRA)" <ji...@apache.org> on 2006/12/22 15:15:21 UTC
[jira] Commented: (AXIS2-1863) problem with
org.apache.axis2.databinding.utils.ConverterUtil.convertTodateTime(String
content)
[ http://issues.apache.org/jira/browse/AXIS2-1863?page=comments#action_12460486 ]
Lee Surprenant commented on AXIS2-1863:
---------------------------------------
Just noticed this issue is also mentioned in comments for http://issues.apache.org/jira/browse/AXIS2-820. Does this count as a duplicate? Either way, time zones need to be handled correctly in both convertToString(Calendar) and ConverterUtil.convertTodateTime(String content)
> problem with org.apache.axis2.databinding.utils.ConverterUtil.convertTodateTime(String content)
> -----------------------------------------------------------------------------------------------
>
> Key: AXIS2-1863
> URL: http://issues.apache.org/jira/browse/AXIS2-1863
> Project: Apache Axis 2.0 (Axis2)
> Issue Type: Bug
> Components: databinding
> Affects Versions: 1.0, 1.1
> Environment: winXP
> Reporter: Lee Surprenant
> Assigned To: Amila Chinthaka Suriarachchi
>
> I am using the dateTime databinding for a simple java.util.Calendar. For instance, when I send the SOAP envelope, the Calendar instance is correctly converted to GMT and I have:
> <dateTime>2006-12-11T23:57:16.625Z</dateTime>
> However, on the other end, calling convertTodateTime() on this string returns a java.util.Calendar object which rerpresents 2006-12-12T4:57:16:625Z.
> This occurs due to the order of the following code:
> calendar = Calendar.getInstance();
> ...
> date = zulu.parse(source.substring(0,19) + ".000Z"); //date is set to Mon Dec 11 23:57:16 EST 2006
> ...
> calendar.setTimeZone(TimeZone.getTimeZone("GMT")); //calendar is set to GMT
> ...
> calendar.setTime(date); //calendar is incorrectly set to 2006-12-12T4:57:16:625Z
> The code has the comment "Note - We only follow the convention in the latest schema spec" but the functionality still doesn't seem correct.
--
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
---------------------------------------------------------------------
To unsubscribe, e-mail: axis-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-dev-help@ws.apache.org