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: [EMAIL PROTECTED] ReportedBy: [EMAIL PROTECTED] 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.
