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
When serializing a array of primitives int[], String[], byte[], etc. the expected output should be something like:
{ "@class":"int[]","data":[2,25,10] }
instead i get this
[
2,
25,
10,
]
or for byte[] { "@class":"byte[]",data:"3JugnGCdJJ3onqyf..." }
i get this
"3JugnGCdJJ3onqyf.......
Since these (arrays) are not real classes, direct naming of a class is difficult, but there should still be a (syntetic) annotation that describes the data type exactly, since these must also be deserialized correctly again, especially in terms of polymorphic deserialization.
The text was updated successfully, but these errors were encountered:
On Aug 21, 2019, at 3:03 AM, roli8200 ***@***.***> wrote:
When serializing a array of primitives int[], String[], byte[], etc. the expected output should be something like:
{ ***@***.***":"int[]","data":[2,25,10] }
instead i get this
[
2,
25,
10,
]
or for byte[]
{ ***@***.***":"byte[]",data:"3JugnGCdJJ3onqyf..." }
i get this
"3JugnGCdJJ3onqyf.......
Since these (arrays) are not real classes, direct naming of a class is difficult, but there should still be a (syntetic) annotation that describes the data type exactly, since these must also be deserialized correctly again, especially in terms of polymorphic deserialization.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or mute the thread.
When serializing a array of primitives int[], String[], byte[], etc. the expected output should be something like:
instead i get this
or for byte[]
{ "@class":"byte[]",data:"3JugnGCdJJ3onqyf..." }
i get this
"3JugnGCdJJ3onqyf.......
Since these (arrays) are not real classes, direct naming of a class is difficult, but there should still be a (syntetic) annotation that describes the data type exactly, since these must also be deserialized correctly again, especially in terms of polymorphic deserialization.
The text was updated successfully, but these errors were encountered: