JSON parser converts null values to the string "null" about protostuff-googlecode-exported

[GoogleCodeExporter]

Sorry for being so late. I forgot to setup notifications on the issues :/

Original comment by [email protected] on 6 Mar 2010 at 4:58

[GoogleCodeExporter]

This seems to be a problem for other nullable values as well ... not just 
strings.
Plus, the Message.Builder will throw an NPE if the string you set is null.
We could call clearFoo() instead if the string is null.
I've modified the patch (fixnull2.patch)

Let me know what you think.

Thanks.

Original comment by [email protected] on 6 Mar 2010 at 7:15

Attachments:

• fixnull2.patch

[GoogleCodeExporter]

You're right that in Protobuf we shouldn't be setting fields to Null, but rather
avoid setting them at all. I submitted this issue a while back, so I no longer
remember if I encountered this problem because of a bug on my part or something 
more
substantial. I would go with your patch.

Original comment by [email protected] on 6 Mar 2010 at 8:11

[GoogleCodeExporter]

Protobuf's native parsing does not have logic for clearing fields upon 
deserialization.
Because of its built-in default-values and required-values support, only fields 
that
are specifically set (null/default values aren't written) are the only ones 
included
on serialization.

In short, protobuf doesn't pass null values around ... 
The logic to explicitly set/clear the values is handled by application code.

Thanks for the report though!  Gave me a lot of thinking to do.

Original comment by [email protected] on 9 Mar 2010 at 3:21

• Changed state: WontFix

[GoogleCodeExporter]

A clear method will prolly have to be added on the gwt-overlay code to clear a
property so it won't be included on serialization.

See http://code.google.com/p/protostuff/issues/detail?id=7

Original comment by [email protected] on 9 Mar 2010 at 3:28

[GoogleCodeExporter]

Looking back at this issue ... I do think this still need to be addressed since
messages with "null" values are unacceptable.

Also jackson's parser converts int values to String if calling getText()

The fix is strictly allowing only the token: JsonToken.VALUE_STRING.
New patch attached/applied (rev 678)

Original comment by [email protected] on 7 May 2010 at 3:42

• Changed state: Fixed

Attachments:

• fix-string-null.patch