On 2010-03-18, at 12:15 PM, BobV wrote:
> The code that you posted is about creating a payload for a object that
> has custom serialization. What does looking at the fields of the
> InvokeCustomFieldSerializerCommand object show?
I can reproduce this in a barebones project. It looks like it's this class
we're using to avoid RPC pulling in all the subclasses of HashMap. We have
similar classes for ArrayList and HashSet, but those all have custom
serializers. I don't know why I didn't create a custom serializer for this
class as well (though there aren't any ill effects with standard RPC).
public final class RpcMap<T, V> extends HashMap<T, V> implements IsSerializable
{
private static final long serialVersionUID = 0L;
public RpcMap() {
}
public RpcMap(final Map<T, V> map) {
super(map);
}
public static <X, Y> RpcMap<X, Y> wrap(final Map<X, Y> map) {
return map == null ? null : new RpcMap<X, Y>(map);
}
}
Here are the fields of InvokeCustomFieldSerializerCommand:
x InvokeCustomFieldSerializerCommand (id=59)
instantiatedType Class<T> (com.dotspots.rpctest.client.RpcMap)
(id=102)
manuallySerializedType Class<T> (java.util.HashMap) (id=107)
serializer Class<T>
(com.google.gwt.user.client.rpc.core.java.util.HashMap_CustomFieldSerializer)
(id=108)
setters ArrayList<E> (id=109)
values ArrayList<E> (id=116)
Matt.
--
http://groups.google.com/group/Google-Web-Toolkit-Contributors
To unsubscribe from this group, send email to
google-web-toolkit-contributors+unsubscribegooglegroups.com or reply to this
email with the words "REMOVE ME" as the subject.
