Skip to content

Commit d65cf18

Browse files
author
fangyidong
committed
init
0 parents  commit d65cf18

24 files changed

+2044
-0
lines changed

.classpath

+8
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,8 @@
1+
<?xml version="1.0" encoding="UTF-8"?>
2+
<classpath>
3+
<classpathentry excluding="**/.svn|**/.svn/**/*" kind="src" output="build/main" path="src"/>
4+
<classpathentry excluding="**/.svn|**/.svn/**/*" kind="src" output="build/test" path="test"/>
5+
<classpathentry kind="con" path="org.eclipse.jdt.launching.JRE_CONTAINER"/>
6+
<classpathentry kind="con" path="org.eclipse.jdt.junit.JUNIT_CONTAINER/3.8.1"/>
7+
<classpathentry kind="output" path="build/main"/>
8+
</classpath>

.project

+17
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,17 @@
1+
<?xml version="1.0" encoding="UTF-8"?>
2+
<projectDescription>
3+
<name>json.simple</name>
4+
<comment></comment>
5+
<projects>
6+
</projects>
7+
<buildSpec>
8+
<buildCommand>
9+
<name>org.eclipse.jdt.core.javabuilder</name>
10+
<arguments>
11+
</arguments>
12+
</buildCommand>
13+
</buildSpec>
14+
<natures>
15+
<nature>org.eclipse.jdt.core.javanature</nature>
16+
</natures>
17+
</projectDescription>

AUTHORS.txt

+1
Original file line numberDiff line numberDiff line change
@@ -0,0 +1 @@
1+
Fang Yidong <[email protected]>

ChangeLog.txt

+11
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,11 @@
1+
ChangeLog
2+
3+
Version 1.01 (2008/08/26)
4+
* License changed to a more commerce friendly and clear one, Apache License 2.0
5+
* Use JFlex to generate a faster Yylex.java
6+
* Added Rope.java to get faster string operations
7+
* Separate test codes from source codes
8+
* Added ant build file build.xml
9+
10+
Version 1.0 (2006/04/15)
11+
* Initial version

LICENSE.txt

+202
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,202 @@
1+
2+
Apache License
3+
Version 2.0, January 2004
4+
http://www.apache.org/licenses/
5+
6+
TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
7+
8+
1. Definitions.
9+
10+
"License" shall mean the terms and conditions for use, reproduction,
11+
and distribution as defined by Sections 1 through 9 of this document.
12+
13+
"Licensor" shall mean the copyright owner or entity authorized by
14+
the copyright owner that is granting the License.
15+
16+
"Legal Entity" shall mean the union of the acting entity and all
17+
other entities that control, are controlled by, or are under common
18+
control with that entity. For the purposes of this definition,
19+
"control" means (i) the power, direct or indirect, to cause the
20+
direction or management of such entity, whether by contract or
21+
otherwise, or (ii) ownership of fifty percent (50%) or more of the
22+
outstanding shares, or (iii) beneficial ownership of such entity.
23+
24+
"You" (or "Your") shall mean an individual or Legal Entity
25+
exercising permissions granted by this License.
26+
27+
"Source" form shall mean the preferred form for making modifications,
28+
including but not limited to software source code, documentation
29+
source, and configuration files.
30+
31+
"Object" form shall mean any form resulting from mechanical
32+
transformation or translation of a Source form, including but
33+
not limited to compiled object code, generated documentation,
34+
and conversions to other media types.
35+
36+
"Work" shall mean the work of authorship, whether in Source or
37+
Object form, made available under the License, as indicated by a
38+
copyright notice that is included in or attached to the work
39+
(an example is provided in the Appendix below).
40+
41+
"Derivative Works" shall mean any work, whether in Source or Object
42+
form, that is based on (or derived from) the Work and for which the
43+
editorial revisions, annotations, elaborations, or other modifications
44+
represent, as a whole, an original work of authorship. For the purposes
45+
of this License, Derivative Works shall not include works that remain
46+
separable from, or merely link (or bind by name) to the interfaces of,
47+
the Work and Derivative Works thereof.
48+
49+
"Contribution" shall mean any work of authorship, including
50+
the original version of the Work and any modifications or additions
51+
to that Work or Derivative Works thereof, that is intentionally
52+
submitted to Licensor for inclusion in the Work by the copyright owner
53+
or by an individual or Legal Entity authorized to submit on behalf of
54+
the copyright owner. For the purposes of this definition, "submitted"
55+
means any form of electronic, verbal, or written communication sent
56+
to the Licensor or its representatives, including but not limited to
57+
communication on electronic mailing lists, source code control systems,
58+
and issue tracking systems that are managed by, or on behalf of, the
59+
Licensor for the purpose of discussing and improving the Work, but
60+
excluding communication that is conspicuously marked or otherwise
61+
designated in writing by the copyright owner as "Not a Contribution."
62+
63+
"Contributor" shall mean Licensor and any individual or Legal Entity
64+
on behalf of whom a Contribution has been received by Licensor and
65+
subsequently incorporated within the Work.
66+
67+
2. Grant of Copyright License. Subject to the terms and conditions of
68+
this License, each Contributor hereby grants to You a perpetual,
69+
worldwide, non-exclusive, no-charge, royalty-free, irrevocable
70+
copyright license to reproduce, prepare Derivative Works of,
71+
publicly display, publicly perform, sublicense, and distribute the
72+
Work and such Derivative Works in Source or Object form.
73+
74+
3. Grant of Patent License. Subject to the terms and conditions of
75+
this License, each Contributor hereby grants to You a perpetual,
76+
worldwide, non-exclusive, no-charge, royalty-free, irrevocable
77+
(except as stated in this section) patent license to make, have made,
78+
use, offer to sell, sell, import, and otherwise transfer the Work,
79+
where such license applies only to those patent claims licensable
80+
by such Contributor that are necessarily infringed by their
81+
Contribution(s) alone or by combination of their Contribution(s)
82+
with the Work to which such Contribution(s) was submitted. If You
83+
institute patent litigation against any entity (including a
84+
cross-claim or counterclaim in a lawsuit) alleging that the Work
85+
or a Contribution incorporated within the Work constitutes direct
86+
or contributory patent infringement, then any patent licenses
87+
granted to You under this License for that Work shall terminate
88+
as of the date such litigation is filed.
89+
90+
4. Redistribution. You may reproduce and distribute copies of the
91+
Work or Derivative Works thereof in any medium, with or without
92+
modifications, and in Source or Object form, provided that You
93+
meet the following conditions:
94+
95+
(a) You must give any other recipients of the Work or
96+
Derivative Works a copy of this License; and
97+
98+
(b) You must cause any modified files to carry prominent notices
99+
stating that You changed the files; and
100+
101+
(c) You must retain, in the Source form of any Derivative Works
102+
that You distribute, all copyright, patent, trademark, and
103+
attribution notices from the Source form of the Work,
104+
excluding those notices that do not pertain to any part of
105+
the Derivative Works; and
106+
107+
(d) If the Work includes a "NOTICE" text file as part of its
108+
distribution, then any Derivative Works that You distribute must
109+
include a readable copy of the attribution notices contained
110+
within such NOTICE file, excluding those notices that do not
111+
pertain to any part of the Derivative Works, in at least one
112+
of the following places: within a NOTICE text file distributed
113+
as part of the Derivative Works; within the Source form or
114+
documentation, if provided along with the Derivative Works; or,
115+
within a display generated by the Derivative Works, if and
116+
wherever such third-party notices normally appear. The contents
117+
of the NOTICE file are for informational purposes only and
118+
do not modify the License. You may add Your own attribution
119+
notices within Derivative Works that You distribute, alongside
120+
or as an addendum to the NOTICE text from the Work, provided
121+
that such additional attribution notices cannot be construed
122+
as modifying the License.
123+
124+
You may add Your own copyright statement to Your modifications and
125+
may provide additional or different license terms and conditions
126+
for use, reproduction, or distribution of Your modifications, or
127+
for any such Derivative Works as a whole, provided Your use,
128+
reproduction, and distribution of the Work otherwise complies with
129+
the conditions stated in this License.
130+
131+
5. Submission of Contributions. Unless You explicitly state otherwise,
132+
any Contribution intentionally submitted for inclusion in the Work
133+
by You to the Licensor shall be under the terms and conditions of
134+
this License, without any additional terms or conditions.
135+
Notwithstanding the above, nothing herein shall supersede or modify
136+
the terms of any separate license agreement you may have executed
137+
with Licensor regarding such Contributions.
138+
139+
6. Trademarks. This License does not grant permission to use the trade
140+
names, trademarks, service marks, or product names of the Licensor,
141+
except as required for reasonable and customary use in describing the
142+
origin of the Work and reproducing the content of the NOTICE file.
143+
144+
7. Disclaimer of Warranty. Unless required by applicable law or
145+
agreed to in writing, Licensor provides the Work (and each
146+
Contributor provides its Contributions) on an "AS IS" BASIS,
147+
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
148+
implied, including, without limitation, any warranties or conditions
149+
of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
150+
PARTICULAR PURPOSE. You are solely responsible for determining the
151+
appropriateness of using or redistributing the Work and assume any
152+
risks associated with Your exercise of permissions under this License.
153+
154+
8. Limitation of Liability. In no event and under no legal theory,
155+
whether in tort (including negligence), contract, or otherwise,
156+
unless required by applicable law (such as deliberate and grossly
157+
negligent acts) or agreed to in writing, shall any Contributor be
158+
liable to You for damages, including any direct, indirect, special,
159+
incidental, or consequential damages of any character arising as a
160+
result of this License or out of the use or inability to use the
161+
Work (including but not limited to damages for loss of goodwill,
162+
work stoppage, computer failure or malfunction, or any and all
163+
other commercial damages or losses), even if such Contributor
164+
has been advised of the possibility of such damages.
165+
166+
9. Accepting Warranty or Additional Liability. While redistributing
167+
the Work or Derivative Works thereof, You may choose to offer,
168+
and charge a fee for, acceptance of support, warranty, indemnity,
169+
or other liability obligations and/or rights consistent with this
170+
License. However, in accepting such obligations, You may act only
171+
on Your own behalf and on Your sole responsibility, not on behalf
172+
of any other Contributor, and only if You agree to indemnify,
173+
defend, and hold each Contributor harmless for any liability
174+
incurred by, or claims asserted against, such Contributor by reason
175+
of your accepting any such warranty or additional liability.
176+
177+
END OF TERMS AND CONDITIONS
178+
179+
APPENDIX: How to apply the Apache License to your work.
180+
181+
To apply the Apache License to your work, attach the following
182+
boilerplate notice, with the fields enclosed by brackets "[]"
183+
replaced with your own identifying information. (Don't include
184+
the brackets!) The text should be enclosed in the appropriate
185+
comment syntax for the file format. We also recommend that a
186+
file or class name and description of purpose be included on the
187+
same "printed page" as the copyright notice for easier
188+
identification within third-party archives.
189+
190+
Copyright [yyyy] [name of copyright owner]
191+
192+
Licensed under the Apache License, Version 2.0 (the "License");
193+
you may not use this file except in compliance with the License.
194+
You may obtain a copy of the License at
195+
196+
http://www.apache.org/licenses/LICENSE-2.0
197+
198+
Unless required by applicable law or agreed to in writing, software
199+
distributed under the License is distributed on an "AS IS" BASIS,
200+
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
201+
See the License for the specific language governing permissions and
202+
limitations under the License.

README.txt

+153
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,153 @@
1+
Simple Java toolkit for JSON (JSON.simple)
2+
==========================================
3+
4+
http://www.JSON.org/java/json_simple.zip
5+
6+
1.Why the Simple Java toolkit (also named as JSON.simple) for JSON?
7+
8+
When I use JSON as the data exchange format between the AJAX client and JSP
9+
for the first time, what worry me mostly is how to encode Java strings and
10+
numbers correctly in the server side so the AJAX client will receive a well
11+
formed JSON data. When I looked into the 'JSON in Java' directory in JSON
12+
website,I found that wrappers to JSONObject and JSONArray can be simpler,
13+
due to the simplicity of JSON itself. So I wrote the JSON.simple package.
14+
15+
2.Is it simple,really?
16+
17+
I think so. Take an example:
18+
19+
import org.json.simple.JSONObject;
20+
21+
JSONObject obj=new JSONObject();
22+
obj.put("name","foo");
23+
obj.put("num",new Integer(100));
24+
obj.put("balance",new Double(1000.21));
25+
obj.put("is_vip",new Boolean(true));
26+
obj.put("nickname",null);
27+
System.out.print(obj);
28+
29+
Result:
30+
{"nickname":null,"num":100,"balance":1000.21,"is_vip":true,"name":"foo"}
31+
32+
The JSONObject.toString() will escape controls and specials correctly.
33+
34+
3.How to use JSON.simple in JSP?
35+
36+
Take an example in JSP:
37+
38+
<%@page contentType="text/html; charset=UTF-8"%>
39+
<%@page import="org.json.simple.JSONObject"%>
40+
<%
41+
JSONObject obj=new JSONObject();
42+
obj.put("name","foo");
43+
obj.put("num",new Integer(100));
44+
obj.put("balance",new Double(1000.21));
45+
obj.put("is_vip",new Boolean(true));
46+
obj.put("nickname",null);
47+
out.print(obj);
48+
out.flush();
49+
%>
50+
51+
So the AJAX client will get the responseText.
52+
53+
4.Some details about JSONObject?
54+
55+
JSONObject inherits java.util.HashMap,so it don't have to worry about the
56+
mapping things between keys and values. Feel free to use the Map methods
57+
like get(), put(), and remove() and others. JSONObject.toString() will
58+
combine key value pairs to get the JSON data string. Values will be escaped
59+
into JSON quote string format if it's an instance of java.lang.String. Other
60+
type of instance like java.lang.Number,java.lang.Boolean,null,JSONObject and
61+
JSONArray will NOT escape, just take their java.lang.String.valueOf() result.
62+
null value will be the JSON 'null' in the result.
63+
64+
It's still correct if you put an instance of JSONObject or JSONArray into an
65+
instance of JSONObject or JSONArray. Take the example about:
66+
67+
JSONObject obj2=new JSONObject();
68+
obj2.put("phone","123456");
69+
obj2.put("zip","7890");
70+
obj.put("contact",obj2);
71+
System.out.print(obj);
72+
73+
Result:
74+
{"nickname":null,"num":100,"contact":{"phone":"123456","zip":"7890"},"balance":1000.21,"is_vip":true,"name":"foo"}
75+
76+
The method JSONObject.escape() is used to escape Java string into JSON quote
77+
string. Controls and specials will be escaped correctly into \b,\f,\r,\n,\t,
78+
\",\\,\/,\uhhhh.
79+
80+
5.Some detail about JSONArray?
81+
82+
org.json.simple.JSONArray inherits java.util.ArrayList. Feel free to use the
83+
List methods like get(),add(),remove(),iterator() and so on. The rules of
84+
JSONArray.toString() is similar to JSONObject.toString(). Here's the example:
85+
86+
import org.json.simple.JSONArray;
87+
88+
JSONArray array=new JSONArray();
89+
array.add("hello");
90+
array.add(new Integer(123));
91+
array.add(new Boolean(false));
92+
array.add(null);
93+
array.add(new Double(123.45));
94+
array.add(obj2);//see above
95+
System.out.print(array);
96+
97+
Result:
98+
["hello",123,false,null,123.45,{"phone":"123456","zip":"7890"}]
99+
100+
6.What is JSONValue for?
101+
102+
org.json.simple.JSONValue is use to parse JSON data into Java Object.
103+
In JSON, the topmost entity is JSON value, not the JSON object. But
104+
it's not necessary to wrap JSON string,boolean,number and null again,
105+
for the Java has already had the according classes: java.lang.String,
106+
java.lang.Boolean,java.lang.Number and null. The mapping is:
107+
108+
JSON Java
109+
------------------------------------------------
110+
string <=> java.lang.String
111+
number <=> java.lang.Number
112+
true|false <=> java.lang.Boolean
113+
null <=> null
114+
array <=> org.json.simple.JSONArray
115+
object <=> org.json.simple.JSONObject
116+
------------------------------------------------
117+
118+
JSONValue has only one kind of method, JSONValue.parse(), which receives
119+
a java.io.Reader or java.lang.String. Return type of JSONValue.parse()
120+
is according to the mapping above. If the input is incorrect in syntax or
121+
there's exceptions during the parsing, I choose to return null, ignoring
122+
the exception: I have no idea if it's a serious implementaion, but I think
123+
it's convenient to the user.
124+
125+
Here's the example:
126+
127+
String s="[0,{\"1\":{\"2\":{\"3\":{\"4\":[5,{\"6\":7}]}}}}]";
128+
Object obj=JSONValue.parse(s);
129+
JSONArray array=(JSONArray)obj;
130+
System.out.println(array.get(1));
131+
JSONObject obj2=(JSONObject)array.get(1);
132+
System.out.println(obj2.get("1"));
133+
134+
Result:
135+
{"1":{"2":{"3":{"4":[5,{"6":7}]}}}}
136+
{"2":{"3":{"4":[5,{"6":7}]}}}
137+
138+
7.About the author.
139+
140+
I'm a Java EE developer on Linux.
141+
I'm working on web systems and information retrieval systems.
142+
I also develop 3D games and Flash games.
143+
144+
You can contact me through:
145+
Fang Yidong<[email protected]>
146+
Fang Yidong<[email protected]>
147+
148+
8.Project home.
149+
150+
http://code.google.com/p/json-simple/
151+
152+
153+
http://www.JSON.org/java/json_simple.zip

0 commit comments

Comments
 (0)