I think passing string representation along with a pattern would be more interoperable. Almost all platforms support dates in string format and patterns are pretty much standard too. Passing long value may not be desirable due to differences in implementation.
Jai -----Original Message----- From: Tim K. (Gmane) [mailto:[EMAIL PROTECTED] Sent: Thursday, March 24, 2005 1:03 PM To: axis-user@ws.apache.org Subject: Re: Axis and .NET interop with dates So is there a way to make a Java Date/Calendar just interoperate with the .NET DateTime type whithout any of the sides to make any conversions? I understand that in .NET DateTime can be converted to a long but it represents "the number of 100-nanosecond intervals that have elapsed since 12:00 A.M., January 1, 0001" Tim James Black wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > Tim K. (Gmane) wrote: > | If you have a Java method to be exposed as a web service that returns a > | date or takes as input a date, what should the Java type be? Date, > | Calendar, long, String representation? > > ~ I use long, and pass the unix time, or > DD:MM:YY HH:MM:SS > though the second part is optional, but I have to dictate the pattern to > use, and this is a string, for my .net clients. > > - -- > "Love is mutual self-giving that ends in self-recovery." Fulton Sheen > James Black [EMAIL PROTECTED] > -----BEGIN PGP SIGNATURE----- > Version: GnuPG v1.2.5 (MingW32) > Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org > > iD8DBQFCQw2GikQgpVn8xrARAo2nAJkBbEMsZap3SViBzicTlLdC2V2qfwCgjuB/ > Jk9rQnBaj/JNiwa3xhGhEcs= > =tywm > -----END PGP SIGNATURE----- >
