I would add that .Net has a problem with dates that are defined in your schema as nillable="true". Might be safer to just pass around strings and tell your client what is the format to use - ie, dates in UCT, in yyyymmddhhss format.
references: http://wiki.apache.org/ws/FrontPage/Axis/DotNetInterop http://blogs.msdn.com/smguest/archive/2004/05/07/128113.aspx http://msdn.microsoft.com/library/default.asp?url=/library/en-us/cpref/html/frlrfSystemXmlSerializationXmlSerializerClassTopic.asp ellecer On Fri, 25 Mar 2005 08:52:32 -0500, Christian faucher <[EMAIL PROTECTED]> wrote: > Hi, > > As another standardized way of passing date, you should consider julian dates. > > Julian dates are a integer, being the number of days since January 1, > 4713 BC at noon (not midnight). You can also add a fraction of days, > being the number of seconds elapsed since noon. > > Julian dates can be represnted as integers (for a precision to the > day) or as double (for a precision to the millis). > > You can google algorihtms to convert back and forth between julian and > gregorian dates, including support for February 29th and the leap that > occured in 15-ish from Oct, 4 to Oct. 15. > > Just my 5 cents... > > Christian Faucher >
