Vlad, Actually I implemented 2 custom serializers: one for null strings and another for null objects. But I think that it looks like a "workaround" for me.
On Thu, Jun 16, 2016 at 4:44 PM, Vladislav Pyatkov <vpyat...@gridgain.com> wrote: > Hello, > > Why do you want this, if you can save full compatibility using custom > serializer for null value (ObjectMapper#setSerializerProvider)? > > On Thu, Jun 16, 2016 at 12:15 PM, Alexey Kuznetsov < > akuznet...@gridgain.com> wrote: > >> Hi All! >> >> I'm working on migrating from outdated json-lib to Jackson issue >> IGNITE-3277 [1] and found that previous library serialize null strings as >> "" and null objects as "null", for example: >> {"a": "", "b": null} >> >> How about to serialize all values as "null" ? >> In this case we would definitely know that in Java before serialization >> to JSON was really NULL, not empty string. >> >> But this may break compatibility in some cases. >> >> Thoughts? >> >> >> 1. https://issues.apache.org/jira/browse/IGNITE-3277 >> >> -- >> Alexey Kuznetsov >> GridGain Systems >> www.gridgain.com >> > > -- Alexey Kuznetsov GridGain Systems www.gridgain.com