But is the same time. I think gwt serialize the long value of the time and
then create a date in client side with this value. Is this correct?
2011/4/1 Brendan Doherty bren...@propertysimplified.com
How will noon fix the problem?
Assuming your server is running on central time (UTC-6) and you
The standard GWT RPC serialization for dates writes out the long value, so that
should be sent correctly. The error comes because when you convert that long to
a string, you do so in a particular timezone, and your choice of timezone can
change the day that you think this time point occurred
This is the reason we created the UTCDateBox. We only send a Long back
and forth between the client and server and that Long always
represents midnight in UTC. This avoids confusion when users in
different time zones are choosing dates.
You can see the UTCDateBox demo and source:
Has anybody noticed a problem with dates and RPC. Basically I receive a date
from the backend and able to see the correct date in the RPC Impl in the
debugger but when I set the Date field on the client (after the the results
are serialized), I see that the date is offset by a day.
I havnt tested
How are you do when I set the Date field on the client?
The serialization to server-client is Ok, but to client-server fail?
Juan
2011/3/31 SVR svr...@gmail.com
Has anybody noticed a problem with dates and RPC. Basically I receive a
date from the backend and able to see the correct date in
Serialization from Client to Server is OK, but Server to Client fails.
I enter say Jan 31, 1979 (a simple Text with DatePicker) and it get saved to
the Database as such, but when I get back the value from the server, I can
see the correct value in the server (RPC Impl) as Jan 31, 1979, but when it
You sent the date to client via a asynchCall. So you receive onSuccesfull or
onFailure. You are update in onSuccesful the date of the simple text
with which value? Can you share the relevant code?
Are you use DateBox?
Juan
2011/3/31 SVR svr...@gmail.com
Serialization from Client to Server is
Simplifying my use case:
I have a Text box from which I read the value from:
Sender is a shared datastore between the client and the server and is of the
form:
Sender{
java.util.date dateOfBirth;
}
GWT Client Side:
TextBox birthDate;
String medDateFormat =
Pretty sure this is a simple issue of the timezone messing things up.
(Sorry for not having a solution right off, just something to look
into.)
On Thu, Mar 31, 2011 at 4:03 PM, SVR svr...@gmail.com wrote:
Simplifying my use case:
I have a Text box from which I read the value from:
Sender is
Check if the value returned by public long Date.getTime() are different.
In dabase is store correctly suppose.
2011/3/31 Josh Berry tae...@gmail.com
Pretty sure this is a simple issue of the timezone messing things up.
(Sorry for not having a solution right off, just something to look
I've experienced and have had to deal with this problem. It is a
timezone related problem. Here's an example.
1) You initialize a Date object from the database on the server side.
Say the date in the database is March 15. Your Date object will be
initialized to March 15 at midnight, because a
On 31. mars 2011 22:33, cri wrote:
The solution that I've always used is to pass dates between the GWT
client and server as Strings, e.g. MM/dd/.
Or set the time component to noon instead of midnight.
M.
--
You received this message because you are subscribed to the Google Groups Google
How will noon fix the problem?
Assuming your server is running on central time (UTC-6) and you pass it to a
client I'm running here in New Zealand (currently UTC+13), your March 15
noon will become March 16 6am. You'll still be a day off.
--
You received this message because you are
13 matches
Mail list logo
