Why don't you just use Date.getTime() and Calendar.setTimeInMillis() on the serverside?
On Jul 10, 3:11 pm, Monica <[email protected]> wrote: > thakker, > > I have the same issue as well, we are live in production and found > this issue for users accessing from a different timezone , we pushed > in a temp fix locally by overriding the default behavior of GWT Date, > the solution provided in the below link, and it worked. > > http://groups.google.com/group/Google-Web-Toolkit/browse_thread/threa... > > But We would like to know if there are any other fix or > recommendations which could be implemented without affecting the > client files, Any recommendation would be highly appreciated. > > Thanks > > On Jul 10, 2:39 pm, "b.thakker" <[email protected]> wrote: > > > I have an issue where, when a java.util.Date is sent via an RPC from > > another time zone than the server, the date changes on the server due > > to the server interpreting the long sent via RPC from the client into > > its own time zone. > > > I am able to get past this issue by implementing the solution provided > > here:http://groups.google.com/group/Google-Web-Toolkit/browse_thread/threa... > > > The problem with this solution is it affects both client and server. > > > I'd like to ask, if anyone knows of a way how we could apply this > > change without affecting the client as I'd prefer making only server- > > side changes and not change the large number of client-side files. > > > I'd highly appreciate any related information. > > > Regards. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/Google-Web-Toolkit?hl=en -~----------~----~----~----~------~----~------~--~---
