It's a lightweight data exchange format and mainly it's easy to read and write by a human and generate by machines. To subscribe to this RSS feed, copy and paste this URL into your RSS reader. The bug pointed out by @pacoverflow seems resolved. It only takes a minute to sign up. The easiest way to compare json strings is using JSONCompare from JSONAssert library. The above test illustrates howJSONObject can be referred to as a Map whileJSONArray can refer its elements as aList. It is indirectly referenced from required .class files. As the above example illustrated, the Utilities.asJSONObject(Object) would convert a Java Map to a JSONObject, a more generic API is IJSONValue jsonify(Object object). By default, it enables the following conversions in order: You might have noticed that converting unknown Java objects to their toString()s is not quite reasonable, that is mainly due to missing something likeAutoMapper to serialize/deserialize Java classes to/from JSON Strings that is out of the scope of this project, but the following unit test shows how it can be supported if helper methods are defined: Though not in the scope ofjsonTuples, if there is anAutoMapper alike library to parse the POJOs in your working projects, then it shall be quite convenient to handle literately any Java objects to and from JSON texts. As shown in the basic parsing example, the parsedJSONArray andJSONObject can be accessed as immutable List