Yep, it seems if you do DateTime.Now, it includes timezone info. If you
do new Date(x, y, z), it doesn't (but you can probably add it). This is
how Flex should work - if no timezone is specified, it should ignore
timezones!! :-(
-Original Message-
From: flexcoders@yahoogroups.com
I've read through that thread, and this hardly seems like acceptable
behaviour to me.
We're sending dates from a .NET web service too, and we don't care about
the time. We're plotting them on a calendar. We can't afford to have
dates sent as one thing, and then rolled back to the previous day
Yes - I think it's an issue with 1.1
In our last Flex 2/.NET 2 application we were able to correctly pass date
objects between Flex and .NET
The only thing you have to watchout for is to make sure that the DateTime
object your return from .NET has its Kind set to UTC - if so, it should work
Title: RE: [flexcoders] Re: About dates sent to a webservice. Is this correct?
This doesn't seem to work in .Net 2.0 either. I can send a
date as UTC, but Flex still deals with it in the local timezone, so if we
do:
Alert.show(myService.myMethod.lastResult.startDate.month)
We get the
We're also using .NET 2.0 but our web services do not return time zone
information. They just send 2006-06-26T10:38:54.
- Kelly
-Original Message-
From: flexcoders@yahoogroups.com [mailto:[EMAIL PROTECTED] On
Behalf Of Daniel Tuppeny
Sent: Monday, June 26, 2006 2:41 AM
To:
Yes this is correct. I recently had a long thread about this. What I
was told by Adobe is that If a web service defined the element-type in
WSDL as `dateTime' and sends a value that does not include a time zone
component Flex has to assume that this is UTC time and will
automatically adjust the
6 matches
Mail list logo
