Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Keep original JSON ordering - LinkedHashMap instead of Hashmap #36

Closed
GoogleCodeExporter opened this issue Mar 18, 2015 · 1 comment
Closed

Keep original JSON ordering - LinkedHashMap instead of Hashmap #36

GoogleCodeExporter opened this issue Mar 18, 2015 · 1 comment
Labels
auto-migrated Priority-Medium Type-Defect

Comments

@GoogleCodeExporter
Copy link 

For a project I'm working on I needed the data read my json-simple to adhere to 
the order in which the original JSON string is formatted. 

This can be simply accomplished by extending JSONObject from a LinkedHashMap. 

Would it be an idea to make this simple change in the main version of the 
json-simple library?

Thanks,
Bert Spaan

Original issue reported on code.google.com by bert.sp...@gmail.com on 13 Jan 2011 at 1:19
@GoogleCodeExporter
Copy link
Author 

It is possible to use LinkedHashMap in current implementation. Please refer to 
encoding examples for more information:
http://code.google.com/p/json-simple/wiki/EncodingExamples#Example_1-3_-_Encode_
a_JSON_object_-_Using_Map

Original comment by fangyid...@gmail.com on 14 Jan 2011 at 6:59

  • Changed state: Invalid

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
auto-migrated Priority-Medium Type-Defect
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@GoogleCodeExporter