[gwt] Char sequence "\n" in String messages gets corrupted through PLAIN String serialization in GWT

[fabiangebert]

I am sending JSON over GWT PLAIN serialization (if there is any way of getting the GWT client send plain String without RPC, let me know) and some of the JSON contains multiline. Therefore the server sends:
{body:"this is\na\nmultiline\nmessage"}
But on the client it will arrive as
{body:"this is
a
multiline
message"}
Such that I have to replace [newline] with \n again to make it work
Why is that?

[pierreh]

This is to be expected with a JSON string as you are sending, because
the \n is interpreted in javascript as a newline.

On 9-7-2012 17:02, fabiangebert wrote:

I am sending JSON over GWT PLAIN serialization (if there is any way of getting the GWT client send plain String without RPC, let me know) and some of the JSON contains multiline. Therefore the server sends:
{body:"this is\na\nmultiline\nmessage"}
But on the client it will arrive as
{body:"this is
a
multiline
message"}
Such that I have to replace [newline] with \n again to make it work
Why is that?

---

Reply to this email directly or view it on GitHub:
#494

[fabiangebert]

No, then I wouldn't have the "" bevor each newline. I think the mistake in the RPC deserializer or Atmosphere deserialization is that it converts \n to [newline] and doesn't respect the \ - it should convert \n to \n and not to [newline]
Or am I mistaking?

[pierreh]

Have a look at the changes I made here : https://github.com/pierreh/atmosphere/commits/master
It allows for automatic JSON serialization. Look especially at the gwt-js-demo