Details
-
Type:
Bug
-
Status:
Closed
-
Priority:
Major
-
Resolution: Won't Fix
-
Affects Version/s: None
-
Fix Version/s: None
-
Component/s: Compatibility
-
Labels:None
Description
Deserializing a JSON made by XStream can be problematic if there are
arrays in the object in question
XStream makes a node object-array which is valid XML but not valid
JavaScript 
Refer - http://www.codelifter.com/main/tips/tip_020.shtml
Can we have XStream make object_array instead for the Jettison and
Json drivers ?
Patch included. It might not be ideal, but it fixes the scenario. At least for serializing.
Activity
Patch improved - this is ready to apply, though y'all might to rename an interface
Paul Hammant
added a comment - Patch improved - this is ready to apply, though y'all might to rename an interface Hi Paul,
I remember now, the JSON XStream generates is valid! Have a look at the syntax graph http://www.json.org/. You have missed the difference between
{ "string-array": [
"a",
"b"
]}
and
{ string-array: [
"a",
"b"
]}
The latter is not valid, but the former is. That's the reason XStream uses quotes for the labels and does not care what the string really contains. And, yes, this is used in praxis, see
http://jonathan.tron.name/2007/10/07/javascript-bdd (also have a look into that extraordinary AdventuresInJavaScriptTesting.pdf page 50ff that I've sent you years ago ... hehehe).
Jörg Schaible
added a comment - Hi Paul,
I remember now, the JSON XStream generates is valid! Have a look at the syntax graph http://www.json.org/ . You have missed the difference between
{ "string-array": [
"a",
"b"
]}
and
{ string-array: [
"a",
"b"
]}
The latter is not valid, but the former is. That's the reason XStream uses quotes for the labels and does not care what the string really contains. And, yes, this is used in praxis, see
http://jonathan.tron.name/2007/10/07/javascript-bdd (also have a look into that extraordinary AdventuresInJavaScriptTesting.pdf page 50ff that I've sent you years ago ... hehehe). Hi Paul,
I thought now some time about this, but I don't like to go down the XmlFriendlyReplacer route again. The generated JSON is valid and its a limitation of a 3rd party JavaScript lib, that causes the problem. However, it is really easy to overcome this, I created an FAQ entry. I'll answer separately on the dev list though.
- Jörg
Jörg Schaible
added a comment - Hi Paul,
I thought now some time about this, but I don't like to go down the XmlFriendlyReplacer route again. The generated JSON is valid and its a limitation of a 3rd party JavaScript lib, that causes the problem. However, it is really easy to overcome this, I created an FAQ entry. I'll answer separately on the dev list though.
Jörg
Closed after receiving no further comment.
Jörg Schaible
added a comment - Closed after receiving no further comment. 
Patch removed, it was not sufficient.