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 bu...@apache.org on 2003/07/08 09:31:42 UTC

DO NOT REPLY [Bug 21394] New: - Possible datetime deserialization bug

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://nagoya.apache.org/bugzilla/show_bug.cgi?id=21394>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND 
INSERTED IN THE BUG DATABASE.

http://nagoya.apache.org/bugzilla/show_bug.cgi?id=21394

Possible datetime deserialization bug

           Summary: Possible datetime deserialization bug
           Product: Axis
           Version: current (nightly)
          Platform: All
        OS/Version: All
            Status: NEW
          Severity: Normal
          Priority: Other
         Component: Serialization/Deserialization
        AssignedTo: axis-dev@ws.apache.org
        ReportedBy: jens@void.fm


I am not 100% sure but it seems the calendar deserializer screws up timezones for non ZULU 
datetime attributes. (see http://marc.theaimsgroup.com/?t=105761151200004&r=1&w=2)

According to http://www.w3.org/TR/xmlschema-2/#dateTime a datetime is based on UTC in case 
it is not ZULU time. However it seems the CalendarDeserializer uses for a non ZULU datetime the 
default java vm timezone, resulting in a wrong date.