[
https://issues.apache.org/jira/browse/TAP5-2098?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13723971#comment-13723971
]
Howard M. Lewis Ship commented on TAP5-2098:
--------------------------------------------
I'm coming around to your line of thinking; there's no reason that the backing
map couldn't be LinkedHashMap.
> JSONObject should keep its properties in the order in which they were added
> ---------------------------------------------------------------------------
>
> Key: TAP5-2098
> URL: https://issues.apache.org/jira/browse/TAP5-2098
> Project: Tapestry 5
> Issue Type: Wish
> Components: tapestry-json
> Affects Versions: 5.3, 5.4
> Reporter: Jochen Kemnade
> Priority: Minor
> Labels: json, patch
>
> While JSON objects are unordered according to the specification, it would be
> nice if Tapestry's implementation kept its properties in the order of their
> insertion. That way, it could be used for pretty-printing more easily.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
