Don't use toString when ser. complex keys of unknown type

[EugenCepoi]

http://stackoverflow.com/questions/30057860/genson-serialization-for-maps-with-complex-keys

[EugenCepoi]

This behaviour can not be changed by default as people expect to ser/de by default a erased Map as a Map<String, Object>.
What can be done is provide an option to ser/de untyped Maps as complex maps. This should also work when runtime type is being used.

[kerler]

+1. Eagerly waiting for your fix.

[aseovic]

JSON object is not a good way to represent Java Maps in general, as it only works in a special case when Map keys are strings. This is why I am amazed that pretty much every JSON serialization framework (including the "standard", JSON-B) tries to do the same, and was pleasantly surprised when I saw that Genson actually treats some maps the way all Java maps should be represented in JSON: as arrays of entries, with keys and values.

What I would really like to see is the ability to treat all the maps that way, with no special handling for string-, int-, long-keyed maps that is currently there.

I know this breaks many assumptions and makes it more difficult to deserialize untyped objects into Map<String, Object> when the serialization of such map would then result in something completely different, but I'd argue that Map<String, Object> is the wrong choice anyway and that untyped objects should be deserialized as javax.json.JsonObject instead.