We support xsd:date. I don't know if that serializer does what you need either. Give it a shot.
-- Tom Jordahl Macromedia Server Development -----Original Message----- From: Shellman, Joel [mailto:[EMAIL PROTECTED] Sent: Monday, July 14, 2003 12:19 PM To: '[EMAIL PROTECTED]' Subject: RE: DO NOT REPLY [Bug 21394] - Possible datetime deserializatio n bug Right. I thought there already was a date type in XML schema and so was asking if Axis already has support for that. -joel -----Original Message----- From: Tom Jordahl [mailto:[EMAIL PROTECTED] Sent: Monday, July 14, 2003 9:08 AM To: '[EMAIL PROTECTED]' Subject: RE: DO NOT REPLY [Bug 21394] - Possible datetime deserializatio n bug You can certainly send an XML element for which you define your own serializer for that would give you any behavior you neeed. -- Tom Jordahl Macromedia Server Development -----Original Message----- From: Shellman, Joel [mailto:[EMAIL PROTECTED] Sent: Monday, July 14, 2003 12:06 PM To: '[EMAIL PROTECTED]' Subject: RE: DO NOT REPLY [Bug 21394] - Possible datetime deserializatio n bug Okay. I think for me then... Does Axis support a date instead of a datetime? Thanks, -joel -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Sent: Monday, July 14, 2003 9:03 AM To: [EMAIL PROTECTED] Subject: DO NOT REPLY [Bug 21394] - 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 ------- Additional Comments From [EMAIL PROTECTED] 2003-07-14 16:02 ------- I am a bit unclear where the bug lies here, but I will say this - Axis send date/time stamps in UTC specifically to avoid the timezone issues that are being raised. It is understood that sending it this way 'looses' the information about what timezone the time was originally in, but the information is still acurrate. Timezones are strictly for 'display' purposes only, relating a UTC time to what part of the world you live in. I would very much be against changing the serializer to emit datetime in any timezone but +0:00. The deserializer however should understand timezones and always do the right thing. Can you summarize specifically what behavior you want to change in Axis?
