Better failure message when parsing a byte[]

Just to make sure I understand, is this with serialization/deserialization? Aside from automatic use of base64 encoding, decoding, it seems dangerous to assume transformations between the two, most likely should throw an exception with meaningful description.

This is regarding parsing, and not parsing of byte "fields" within the json, which are encoded. I mean parse failures that are thrown for example because of a malformed json when using JsonFactory#createJsonParser(byte[] data). For example:

JsonParseException[Numeric value (9223372036854775807) out of range of int\n
at [Source: [B@3ad6a0e0; line: 1, column: 31]];

See the Source: B@..., it would be nice to have it in the String representation as an option (assuming one is willing to pay the price of decoding it into a string for the exception). Maybe it should be on the JsonParseException, on its toString, and then not as an option in the parser (but then users won't be able to control it...)

Ah, I see. I totally misunderstood... hmmh. It definitely should be possible to do something for this case, as well as related case of String input.
It should actually be possible, since in these cases source object is indeed carried along and hence accessible. But need to think of what would make most sense...