Processing Forum

Loading...

Processing Forum

Screen name:
mremillard

mremillard's Profile

2 Posts

0 Responses

0 Followers

Activity Trend

Last 30 days

Loading Chart...

Show:

Expanded view
List view

JSON converts hexadecimal to decimal

[1 Reply]
- 03-Apr-2013 11:00 AM
- Forum: Core Library Questions
If I am running the following java code with json version 20080701:

    String xmlString = "<soap:Envelope xmlns:soap=\"http://schemas.xmlsoap.org/soap/envelope/\"><soap:Body><response><code>0x02FE0921</code></response></soap:Body></soap:Envelope>";
    JSONObject json = XML.toJSONObject(xmlString);

then I get a JSONObject which looks like this:

    {"soap:Envelope":{"soap:Body":{"response":{"code":"0x02FE0921"}},"xmlns:soap":"http://schemas.xmlsoap.org/soap/envelope/"}}

but if I am using json version 20090211 then the same code will get me a JSONObject looking like this:

    {"soap:Envelope":{"soap:Body":{"response":{"code":50202913}},"xmlns:soap":"http://schemas.xmlsoap.org/soap/envelope/"}}

Notice how the "code" is now in decimal (50202913) rather then remaining in hexadecimal (0x02FE0921).

It would appear that in this latest version of the JSON jar they don't assume a String as often as they use to...

Can this be changed? Can we somehow get the same behavior with the 2009011 version as we did with the 20080701 version?

JSON does not allow non-finite numbers

[1 Reply]
- 03-Apr-2013 08:59 AM
- Forum: Core Library Questions
If I am running the following java code using json 20080701 then I have no problem:

    String xmlString = "<Envelope><Body><Id>10e6847</Id></Body></Envelope>";
    JSONObject json = XML.toJSONObject(xmlString);

but if I am using json 20090211 then I get:

    org.json.JSONException: JSON does not allow non-finite numbers.
    at org.json.JSONObject.testValidity(JSONObject.java:1261)
    at org.json.JSONObject.accumulate(JSONObject.java:420)
    at org.json.XML.parse(XML.java:257)
    at org.json.XML.parse(XML.java:263)
    at org.json.XML.parse(XML.java:263)
    at org.json.XML.parse(XML.java:263)
    at org.json.XML.parse(XML.java:263)
    at org.json.XML.toJSONObject(XML.java:302)
    etc...

How do I make it no longer choke on the "10e6847"? How can I tell json to go back to treating this ID as a simple string rather then thinking it is a number?

«Prev
Next »