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
Default implementation of 2.8-added writeEmbeddedObject() throws exception (unsupported operation) for all values, since JSON does not have any native object types.
This is different from handling of writeObject(), which tries to either delegate to ObjectCodec (if one registered), or even encode "simple" values.
However: since support for binary data is already handled in some cases using VALUE_EMBEDDED_OBJECT, it would actually make sense to handle case of byte[] (and, if feasible, perhaps ByteBuffer for extra points), and also ensure null can be written.
(note: should be safe for patch, that is, 2.8.3)
Default implementation of 2.8-added
writeEmbeddedObject()
throws exception (unsupported operation) for all values, since JSON does not have any native object types.This is different from handling of
writeObject()
, which tries to either delegate toObjectCodec
(if one registered), or even encode "simple" values.However: since support for binary data is already handled in some cases using
VALUE_EMBEDDED_OBJECT
, it would actually make sense to handle case ofbyte[]
(and, if feasible, perhapsByteBuffer
for extra points), and also ensurenull
can be written.This is likely necessary to support FasterXML/jackson-databind#1361 and should in general make system more robust.
The text was updated successfully, but these errors were encountered: