Can we also discuss this one:I haven't seen much discussion on this. I would like to close this one with no action. I don't see parsers are operating at byte level so there is no point in exposing the byte array instead of String. If someone really wants to do this, they could write a custom provider that extends JsonParser and provide a custom JsonString that exposes a byte array. So, I don't think it needs to be in the API.
[json-processing-spec users] Re: JSON_PROCESSING_SPEC-1 : Do not require that all content end up in String or char