axis-java-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Andreas Veithen (JIRA)" <>
Subject [jira] Commented: (AXIS2-4152) ConverterUtil.convertToString(Calendar) returns timezone instead of zone offset
Date Tue, 02 Dec 2008 22:22:44 GMT


Andreas Veithen commented on AXIS2-4152:

Exactly, only answers a and b are correct.

Gavin, another convincing argument goes as follows: answer c can't be correct because the
recipient of the information has no way to know that you are actually in Adelaide (where DST
is in effect and the time difference with respect to UTC is +10:30) and not in the +9:30 timezone
on the northern hemisphere where DST is not in effect, i.e. the recipient would not be able
to calculate the time in UTC.

Also, section of "XML Schema Part 2: Datatypes Second Edition" is relatively clear:

"When a timezone is added to a UTC dateTime, the result is the date and time "in that timezone".
For example, 2002-10-10T12:00:00+05:00 is 2002-10-10T07:00:00Z and 2002-10-10T00:00:00+05:00
is 2002-10-09T19:00:00Z."

That rule always holds, whether DST is in effect or not.


> ConverterUtil.convertToString(Calendar) returns timezone instead of zone offset
> -------------------------------------------------------------------------------
>                 Key: AXIS2-4152
>                 URL:
>             Project: Axis 2.0 (Axis2)
>          Issue Type: Bug
>          Components: adb
>    Affects Versions: 1.4.1
>         Environment: Axis 2, Weblogic, java 1.4.2
>            Reporter: Gavin Pearce
> According to my interpretation of the XML Schema spec (
) the zone offset should be returned as part of the date component instead of the timezone.
 This affects regions that have daylight saving time in effect.  In Adelaide we have daylight
saving during the summer period and the value returned from convertToString becomes 2008-11-28T11:01:54.232+10:30
during that period whereas it should remain at 2008-11-28T11:01:54.232+09:30
> This code was changed between release 1.4.0 and 1.4.1.

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:
For additional commands, e-mail:

View raw message