I override onBeforeRequestDeserialized and onAfterResponseSerialized in my servlets to view the raw data being passed in RPC. I have also used HashSet with generics and do not generally have problems. Once, I think it was in an earlier version of GWT, I needed to add any objects that I used generically to a fake method in one of my services. So if the was Set<Foo> and Set<Bar> I would add workaround (Foo arg0, Bar arg1) to any of my remote services. This got around the problem.
On Jan 7, 1:46 pm, rlaferla <robertlafe...@comcast.net> wrote: > How do you guys go about debugging serialization issues? I am using > GWT 1.5.3 and my GWT client is sending a DTO to the server. If I do a > Log.debug() just prior to the call to the server, I see all of my data > in my DTO. However, when I do a log.debug() on my DTO in the GWT-RPC > service, some of my data is missing. I have read through forum posts, > etc... but I feel I don't have the necessary tools to debug the > problem. The data that appears to not be serialized is a > Set<CustomClass> (implementation is a HashSet) off of my DTO. Both > the DTO and CustomClass are marked Serializable, I use generics for > the Set. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group. To post to this group, send email to Google-Web-Toolkit@googlegroups.com To unsubscribe from this group, send email to google-web-toolkit+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/Google-Web-Toolkit?hl=en -~----------~----~----~----~------~----~------~--~---
