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 ------- Additional Comments From [EMAIL PROTECTED] 2003-07-14 15:27 ------- Your test case already succeeds and doesn't cover what I'm trying to do: preserve the timezone. For example, in your test class, add: public void testDeserializeKeepTimeZone() throws Exception { Calendar cal = null; cal = deserialize(easternTime); assertTrue(cal.getTimeZone().hasSameRules(TimeZone.getTimeZone ("EST"))); assertEquals(2003, cal.get(Calendar.YEAR)); assertEquals(6, cal.get(Calendar.MONTH)); assertEquals(8, cal.get(Calendar.DAY_OF_MONTH)); assertEquals(19, cal.get(Calendar.HOUR_OF_DAY)); assertEquals(0, cal.get(Calendar.MINUTE)); assertEquals(0, cal.get(Calendar.SECOND)); assertEquals(0, cal.get(Calendar.MILLISECOND)); } Obviously, this fails. My question is, is it acceptable for it to be written such that this succeeds? We need that. I'll be making changes to Axis to do this today, but I need to know if that is acceptable behavior (ie. is there anything in the spec that disallows us to preserve timezone).
