You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
So: currently binary values (supported by some binary formats, but not textual formats like JSON or XML) can be coerced into String values (see StringDeserializer.deserialize() special case for JsonToken.VALUE_EMBEDDED_OBJECT); same is true for Tree Model based handling.
This is implemented by re-encoding binary as Base64 content.
However, specialized String-value collection/array deserializers are missing this case: they use method "_parseString()" from StdDeserializer.
Given that default String handling does this, it makes sense to support same coercion for container cases.
Note: testing probably needs to be done from format modules as JSON backend can not induce VALUE_EMBEDDED_OBJECT tokens (although testing handling of TokenBuffer might make sense -- maybe easiest still via binary codecs): for example, from cbor backend for which original issue was reported.
The text was updated successfully, but these errors were encountered:
(note: follow-up for FasterXML/jackson-dataformats-binary#188)
So: currently binary values (supported by some binary formats, but not textual formats like JSON or XML) can be coerced into
String
values (seeStringDeserializer.deserialize()
special case forJsonToken.VALUE_EMBEDDED_OBJECT
); same is true for Tree Model based handling.This is implemented by re-encoding binary as Base64 content.
However, specialized String-value collection/array deserializers are missing this case: they use method "_parseString()" from
StdDeserializer
.Given that default String handling does this, it makes sense to support same coercion for container cases.
Note: testing probably needs to be done from format modules as JSON backend can not induce
VALUE_EMBEDDED_OBJECT
tokens (although testing handling ofTokenBuffer
might make sense -- maybe easiest still via binary codecs): for example, from cbor backend for which original issue was reported.The text was updated successfully, but these errors were encountered: