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 Date object encodes an
instant in time, not just a calendar day.
2) Now you pass the Date object to the client layer in a later
timezone, say from Eastern to Central timezones. In the central
timezone March 15 at midnight translates to March 14 at 11pm. So, the
calendar day is off by one.
You get a similar problem when passing dates from the client to the
server.
The solution that I've always used is to pass dates between the GWT
client and server as Strings, e.g. MM/dd/yyyy.
On Mar 31, 3:10 pm, Juan Pablo Gardella <gardellajuanpa...@gmail.com>
wrote:
> 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
> > 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 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 =
> > > locale.getDateTimeFormatInfo().dateFormatMedium();
> > > String dateString = birthDate.getText();
> > > Date date =
> > DateTimeFormat.getFormat(medDateFormat).parse(dateString);
> > > sender.setDateOfBirth(date);
>
> > > This date is being passed to an RPC and stored in the DB.
>
> > > RPC save:
> > > java.sql.Date birthDate = null;
> > > if (sender.getDateOfBirth() != null) {
> > > SimpleDateFormat sqlformat = new SimpleDateFormat(
> > "yyyy-MM-dd"
> > > );
> > > birthDate =
> > > java.sql.Date.valueOf(sqlformat.format(sender.getDateOfBirth()));
> > > }
> > > and birthDate is stored in the DB.
>
> > > So far its fine.
>
> > > When I read back the data:
> > > RPC read method:
> > > java.sql.date date1
> > > sender.setDateOfBirth(date1.getTime());
>
> > > GWT Client:
> > > if (sender.getDateOfBirth() != null)
>
> > > this.birthDate.setText(DateTimeFormat.getFormat(medDateFormat).format(
> > > sender.getDateOfBirth()));
> > > else
> > > birthDate.setText("");
>
> > > Now I see the value on the textBox has changed, is off by a day!
>
> > > On Thu, Mar 31, 2011 at 3:27 PM, Juan Pablo Gardella
> > > <gardellajuanpa...@gmail.com> wrote:
>
> > >> 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 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 comes back to the client after the RPC call, the value is Jan 30,
> > 1979.
>
> > >>> On Thu, Mar 31, 2011 at 3:08 PM, Juan Pablo Gardella
> > >>> <gardellajuanpa...@gmail.com> wrote:
>
> > >>>> 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 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 extensively for what dates cause this problem, but I
> > do
> > >>>>> see this randomly. Yes the Client and the Server are in different
> > time
> > >>>>> zones, but I am not setting the time component (using sql.date on the
> > server
> > >>>>> side, which essentially has no time component).
>
> > >>>>> Anybody has encountered this before? I can work aound this (by
> > passing
> > >>>>> the DD, MM, YYYY components separately), but want to understand the
> > problem
> > >>>>> better.
> > >>>>> Thanks
>
> > >>>>> --
> > >>>>> You received this message because you are subscribed to the Google
> > >>>>> Groups "Google Web Toolkit" group.
> > >>>>> To post to this group, send email to
> > >>>>> google-web-toolkit@googlegroups.com.
> > >>>>> To unsubscribe from this group, send email to
> > >>>>> google-web-toolkit+unsubscr...@googlegroups.com.
> > >>>>> For more options, visit this group at
> > >>>>>http://groups.google.com/group/google-web-toolkit?hl=en.
>
> > >>>> --
> > >>>> You received this message because you are subscribed to the Google
> > >>>> Groups "Google Web Toolkit" group.
> > >>>> To post to this group, send email to
> > >>>> google-web-toolkit@googlegroups.com.
> > >>>> To unsubscribe from this group, send email to
> > >>>> google-web-toolkit+unsubscr...@googlegroups.com.
> > >>>> For more options, visit this group at
> > >>>>http://groups.google.com/group/google-web-toolkit?hl=en.
>
> > >>> --
> > >>> You received this message because you are subscribed to the Google
> > Groups
> > >>> "Google Web Toolkit" group.
> > >>> To post to this group, send email to
> > google-web-toolkit@googlegroups.com.
> > >>> To unsubscribe from this group, send email to
> > >>> google-web-toolkit+unsubscr...@googlegroups.com.
> > >>> For more options, visit this group at
> > >>>http://groups.google.com/group/google-web-toolkit?hl=en.
>
> > >> --
> > >> You received this message because you are subscribed to the Google
> > Groups
> > >> "Google Web Toolkit" group.
> > >> To post to this group, send email to
> > google-web-toolkit@googlegroups.com.
> > >> To unsubscribe from this group, send email to
> > >> google-web-toolkit+unsubscr...@googlegroups.com.
> > >> For more options, visit this group at
> > >>http://groups.google.com/group/google-web-toolkit?hl=en.
>
> > > --
> > > You received this message because you are subscribed to the Google Groups
> > > "Google Web Toolkit" group.
> > > To post to this group, send email to google-web-toolkit@googlegroups.com
> > .
> > > To unsubscribe from this group, send email to
> > > google-web-toolkit+unsubscr...@googlegroups.com.
> > > For more options, visit this group at
> > >http://groups.google.com/group/google-web-toolkit?hl=en.
>
> > --
> > You received this message because you are subscribed to the Google Groups
> > "Google Web Toolkit" group.
> > To post to this group, send email to google-web-toolkit@googlegroups.com.
> > To unsubscribe from this group, send email to
> > google-web-toolkit+unsubscr...@googlegroups.com.
> > For more options, visit this group at
> >http://groups.google.com/group/google-web-toolkit?hl=en.
--
You received this message because you are subscribed to the Google Groups
"Google Web Toolkit" group.
To post to this group, send email to google-web-toolkit@googlegroups.com.
To unsubscribe from this group, send email to
google-web-toolkit+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/google-web-toolkit?hl=en.
