I had a recent search through everything related to this, and I believe you have up-to-date information. Instead of recompiling GWT, I tried putting the custom field serializers in my project and putting that ahead of GWT in the classpath, but I couldn't make it work this way. I went back to recompiling GWT.
I think this use case is way too common for it not to be supported natively by GWT. It's gwt-user.jar that contains the custom field serializers. Don't forget that if you do this, you may need to change the custom field serializers for java.sql.Date and java.sql.Timestamp if your project can also send those via RPC. Paul leslie wrote: > I'm attempting to send Date information from the client to the server > in a different timezone using remote procedure calls. As others have > already have commented, I am experiencing the expected change in value > of the Date because of the difference in the timezone. > > I have found a post which describes the process of making changes to > the Custom Serializer for Date. > http://groups.google.com/group/google-web-toolkit/browse_thread/thread/fd7b80de11507908/2874ac102f17db26?lnk=gst&q=date+serialize#2874ac102f17db26 > > Is this still the appropriate method by which Date information should > be saved and if I need to recompile all of the GWT classes ( I hope > not ) which jar files am I re creating? > > I notice that the thread is over a year and a half old. I was > wondering if any new methods or strategies are available as of GWT 2.0 > > Any information about the process of saving Date information is > appreciated. 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 [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.
