JSON JettisonMappedXmlDriver quoting numeric values breaking JSON 2 Java deserialization Issue

I am not sure about this functionality. While XStream deals with typed objects, Jettison only recognizes String values. With your patch Jettison will always try to use a "better" type - even if the original type in the Java object was really a String. We'll see what the Jettison devs will say, XStream will use what they provide

I agree that there is a major issue where values such as:

String id = "1245";

Jettison will conver to the JSON format:

id:1245

instead of the correct:
id:"1245"

I think the real solution would be to have Jettison recognize typed values and convert them based on their original types instead of what would be the "better" type.

The core issue I was having was lack of support for reading a JSON object to a java object using
T getX()
setX(T item)

Where the JSON string would always use a T of type String instead of what the real type is, but now I've introduced an issue where a String field that can convert to a numeric may not convert back using a setX(String o).

Deserialization works, since the StAX parser will provide XStream a String anyway and XStream will look up the type from the field that has to be written. I've tested it against the head revision of Jettison.

I'm closing this now, since the problem is completely within Jettison. However, the Jettison guys have fixed it already, but I don't know when they will release Jettison again. Current head of XStream or upcoming version 1.3 will run with Jettison newer then version 1.2-RC2.

Closed after no further comment has been given.