Used to be RPC would just not allow these types and you'd get a serialization error, now they work but maybe was better to get the error and deal with it upfront.. Anyways I find it best just to always translate everything that might get sent back to Date as it comes out of your database calls, means less client code and none of these class compatibility issues.
On Apr 30, 1:47 pm, javaunixsolaris <[email protected]> wrote: > Ok through some trial and error I determined the type (181) to be > java.sql.Timestamp. > > This is still a dangerous BUG though, why is GWT changing my object > types? I mean they have typeId$ 22 so I see no reason to convert that > into 181. > -- 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.
