Wonderful. Thanks for the explanation. It makes perfect sense. On Mon, Oct 20, 2008 at 3:35 AM, Lothar Kimmeringer <[EMAIL PROTECTED]>wrote:
> > Larry White schrieb: > > That might have worked, but i worked around the problem. I tracked it > > down to a Serializable object that contained a date that was > > reconstructed from a Postgres DB using Apache's open JPA. > > something like > java.util.Date date = myResultSet.getDate(1); > If yes, the returned date will most likely be of type > java.sql.Date or java.sql.Timestamp. > > Both are derived from java.util.Date, so they can easily be > assigned to members of that type but as soon as you try > to serialize that, the serializer will see java.sql.Date > or java.sql.Timestamp and throw an exception. > > > Regards, Lothar > > > > --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
