Without more information, I would be hesitant to say you've found a bug. The RPC mechanism must be as conservative as possible in its estimates of what can and cannot be serializable, otherwise it would attempt to allow every widget to go across the wire.
A few things to check – does the type which references your HashMap subclass declare it as a HashMap, or by name? If the latter, something else could be stopping your subclass from being available, such as it or a superclass being named in a <set-configuration-property name='rpc.blacklist' /> tag in any module? Otherwise, is it possible you are using the map to hold objects which are never named as explicitly reachable types? An example of this would be declaring a Map<String, Object> and storing various valid, serializable types - though they are legal to send over the wire, GWT can't tell for certain that you will send them, so it removes them. In this case, consider either adding an unused private field of the given type to the type that wraps this, or add the type name to the rpc.whitelist, ensuring that it may always be sent over the wire. Hope this helps - if not, more information on the usecase would be helpful to provide further advice. -- 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.
