ignite-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Alexey Kuznetsov <akuznet...@gridgain.com>
Subject Re: Change rest-http Java to JSON null transformation logic
Date Thu, 16 Jun 2016 10:04:09 GMT
Pavel, in this case object will be serialized like : {"a": "null"} compare
with {"a": null}

On Thu, Jun 16, 2016 at 4:49 PM, Pavel Tupitsyn <ptupitsyn@gridgain.com>
wrote:

> Hi,
>
> What if there is an actual string with "null" value?
>
> Pavel.
>
> On Thu, Jun 16, 2016 at 12:44 PM, Vladislav Pyatkov <vpyatkov@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 <
>> akuznetsov@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

Mime
View raw message