Re: Date Serialization

2012-07-13 Thread Daniel F.
Probably not, because the constant offset is currently 1340029810 seconds which is 15509 days That would be a strange timezone ;-) So there is probably a different reason. Or it lies in the internals of the application from which the data comes and to which I have no access. Daniel (And

Re: Date Serialization

2012-07-13 Thread Paul Robinson
Curiously, 15509 is pretty close to the number of days since Jan 1, 1970 which is when unix timestamps are measured from. According to this: http://www.convertunits.com/dates/daysfromnow/-15509 15509 days ago was Jan 26, 1970. That probably won't help you :) Paul On 13/07/12 09:19,

Re: Date Serialization

2012-07-03 Thread Philippe Lhoste
On 30/06/2012 16:37, Daniel F. wrote: I need to parse serialized *java.util.Date* values in Python. Where can I find information on the timestamp that represents date and time in the serialized format? JavaDoc... http://docs.oracle.com/javase/6/docs/api/java/util/Date.html See getTime() --

Re: Date Serialization

2012-07-03 Thread Daniel F.
Am Dienstag, 3. Juli 2012 14:42:11 UTC+2 schrieb PhiLho: On 30/06/2012 16:37, Daniel F. wrote: I need to parse serialized *java.util.Date* values in Python. Where can I find information on the timestamp that represents date and time in the serialized format? JavaDoc...

Re: Date Serialization

2012-07-03 Thread Paul Robinson
On 03/07/12 21:41, Daniel F. wrote: Am Dienstag, 3. Juli 2012 14:42:11 UTC+2 schrieb PhiLho: On 30/06/2012 16:37, Daniel F. wrote: I need to parse serialized *java.util.Date* values in Python. Where can I find information on the timestamp that represents date and time in the

Re: Date Serialization

2012-07-03 Thread Jim Douglas
Yup, probably the timezone offset. We tripped over that too (wrong dates when the server and client were in different time zones); we stopped serializing Date objects and switched to sending a customized y/m/d value instead. On Jul 3, 2:41 pm, Paul Robinson ukcue...@gmail.com wrote: On 03/07/12

Re: Date Serialization

2012-07-03 Thread Thomas Broyer
On Wednesday, July 4, 2012 12:43:30 AM UTC+2, Jim Douglas wrote: Yup, probably the timezone offset. We tripped over that too (wrong dates when the server and client were in different time zones); we stopped serializing Date objects and switched to sending a customized y/m/d value

Re: Date Serialization

2012-07-03 Thread Joseph Lust
This question comes up so often that it ought to be a priority for GWT 2.6. Perhaps a module setting to for TZ safe date serialization? See the solution of a custom date serializer in this earlier

Re: Date Serialization

2012-07-03 Thread Thomas Broyer
On Wednesday, July 4, 2012 3:17:42 AM UTC+2, Joseph Lust wrote: This question comes up so often that it ought to be a priority for GWT 2.6. Perhaps a module setting to for TZ safe date serialization? If the timezone matters to you, you can simply send it along with the date (timestamp).

Re: Date Serialization in RPC

2012-04-20 Thread dfreis
The problem I still had was in web mode in combination with tomcat. Since it is not easy to control the Classloader in tomcat the gwt-servlet.jar was always loaded prior to my jar named owhatever.jar. I figured out that tomcats classloader order is alway alphabetic so that g*.jar is always

Re: Date Serialization in RPC

2012-04-20 Thread Joseph Lust
Have you implemented the custom date serializer noted in this post? It worked for me when there was a timezone issue between clients and servers being in different regions. http://code.google.com/p/google-web-toolkit/issues/detail?id=5886 Here is my implementation of that solution. Note that

Re: Date Serialization issues

2010-08-09 Thread Ameya Kulkarni
We are sending date objects from server. It works for all dates except the older ones. We cannot change the implementation to send strings now. How do we set time zone in the application ? On Aug 6, 11:26 am, Muhammad bilal_hobn...@yahoo.com wrote: Dear , Please set time zone in your

Re: Date Serialization issues

2010-08-09 Thread Paul Robinson
You can't change the timezone. You can't even create a date on the client and tell it what timezone it should be in - Javascript does not provide a way to do this. If you want dates on the client to appear to be the same time of day and date as it is on the server, regardless of the client's

Re: Date Serialization issues

2010-08-09 Thread AaroeiraA
Hi, You can do something like this: Write custom Date/Time serializers and put them in the root of your project. Like this: Project | - your.package.com | - com.google.gwt.user.client.rpc.core.java.sql | - com.google.gwt.user.client.rpc.core.java.util The custom serializers NEED to be named:

Re: Date Serialization issues

2010-08-06 Thread Bhaskar
Yes... Convert the date into string and send, it will work well let me know if u need more info Regards, Bhaskar On Fri, Aug 6, 2010 at 11:39 AM, Ameya Kulkarni amey...@gmail.com wrote: Hi We are sending java.util.Date objects from the server. On the client side these date values are not

Re: Date Serialization issues

2010-08-06 Thread Muhammad
Dear , Please set time zone in your application. then you may get exact date you want. Muhammad Bilal Ilyas Software Engineer From: Ameya Kulkarni amey...@gmail.com To: Google Web Toolkit google-web-toolkit@googlegroups.com Sent: Fri, August 6, 2010

Re: Date Serialization in RPC

2010-06-02 Thread Lothar Kimmeringer
leslie schrieb: 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. Using

Re: Date Serialization in RPC

2010-06-02 Thread mariyan nenchev
Why don't you use GMT times every where and just use the user's locale to format them in his/her timezone, but internally use Timestamp, or date.getTime() // long in gmt -- You received this message because you are subscribed to the Google Groups Google Web Toolkit group. To post to this group,

Re: Date Serialization in RPC

2010-06-02 Thread Paul Robinson
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

Re: Date Serialization in RPC

2010-06-02 Thread leslie
(I apologize if this appears twice. I thought it was submitted but it appears to have been lost.) Thanks so much Lothar for your response. --Using java.util.Date this comes without surprise, because --Date itself doesn't contain any timezone-information. This is true. --Saved or serialized?

Re: Date Serialization in RPC

2010-06-02 Thread leslie
Thanks marlyan for your repsonse -- Why don't you use GMT times every where I'm not sure what you mean here. I'm using the DateBox for the convenience of my end user on my GWT gui and it returns a Date to the model. That Date is serialized with the model object to be sent to the server. --

Re: Date Serialization in RPC

2010-06-02 Thread leslie
Thanks very much Paul for your response, for sharing your experience and confirming what I guess I suspected. I guess I'm going to go ahead and obtain the src files for the gwt-user jar, swap out the Date Custom Serialization class and recompile and recreate the jar. Fortunately, right now I'm

Re: Date Serialization in RPC

2010-06-02 Thread Lothar Kimmeringer
Hi Leslie, first of all (offtopic), try to conform to the quoting standards. preceding '--'s are not. leslie schrieb: --Saved or serialized? IMHO: --Saved: UTC-times --Serialized: W3C-formatted string representation of the date It looks like you are suggesting that rather than send the

Re: Date Serialization in RPC

2010-06-02 Thread leslie
No luck here.. I tried making the changes found in the file in the link I offered earlier. Running with the new code produces the following error when I attempt to retrieve a list of objects each with a Date attribute. com.google.gwt.dev.shell.HostedModeException: Something other than an int

Re: Date Serialization in RPC

2010-06-02 Thread leslie
Hi Lothar, Thanks again for your help, first of all (offtopic), try to conform to the quoting standards. preceding '--'s are not. Ok. You're right. Sorry about that. We were talking about dates where you need timezones. A birthday is a quite bad example for that. Yes I see your point.

Re: Date Serialization in RPC

2010-06-02 Thread Paul Robinson
I misled you slightlythe date/date/timestamp custom field serializers are also in gwt-servlet.jar Paul leslie wrote: No luck here.. I tried making the changes found in the file in the link I offered earlier. Running with the new code produces the following error when I attempt to

Re: Date Serialization in RPC

2010-06-02 Thread kozura
Or, if all you really want is the actual date entered by the user and don't care about the time, you can simply send mm dd, either as a separate object or parameters to an RPC, and avoid custom serializers, interpreting Universal Date against timezones, or recompiling GWT. Why make sh*t

Re: Date Serialization in RPC

2010-06-02 Thread leslie
I'm converting an existing java desktop application to the web by using GWT. The model classes are already written and they contain a number of Dates. The Person example was a trivial representation of a larger model. What you're suggesting is more complicated than you realize. On Jun 2, 11:44 

Re: Date Serialization in RPC

2010-06-02 Thread leslie
That was it. Recompiling the servlet jar file with the updated Date Custom Serializer class worked. Thanks very much. On Jun 2, 11:11 am, Paul Robinson ukcue...@gmail.com wrote: I misled you slightlythe date/date/timestamp custom field serializers are also in gwt-servlet.jar Paul --