Ian, I'm confused by your statement "coming from server-side code". That's a compile warning against a serializable (shared) class. I have a similar artifact in my project right now. It happens to be caused by a defined type X that extends HashMap<String,String>. It seems as if the compiler is inspecting the OrderedConstantSet, something never referenced in the application, only because it is also a Map<String,String>. I would like to understand if this is necessary or a bug in the compiler.
Thanks, Walden On Oct 31, 7:10 am, "Ian Petersen" <[EMAIL PROTECTED]> wrote: > On Thu, Oct 30, 2008 at 4:38 PM, WebDude <[EMAIL PROTECTED]> wrote: > > If I leave out the "stringMap" member, I do not get the warning. Is > > this a warning I need to worry about? > > The warning is coming from your server-side code, not the definition > of your transfer object. Can you show us what you're sending back to > the client? What kind of instance are you putting in stringMap? > > Ian --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
