KeyValuePair service doesn't serialize user-defined types (RPC)
Bug #786529 reported by
Matt Giuca
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| MUGLE |
Triaged
|
High
|
Unassigned | ||
Bug Description
It is not currently possible for developers to provide their own user-defined class objects as KVP keys or values, as they fail to serialize. The RPC system throws a com.google.
You seem to be able to serialize any primitive type, or class defined in the standard library. You can't serialize array objects, or objects of user-defined type.
We may need to simply change the interface to accept strings or define a rich JSON-like type and allow serialization of that. For now, I have told students to just use built-in types like Vector and HashMap.
Note: This is not a duplicate of bug #744035. That deals with the database serialization; this deals with the RPC.
To post a comment you must log in.
