[ http://issues.apache.org/jira/browse/TAPESTRY-1028?page=all ]

Jesse Kuhnert resolved TAPESTRY-1028.
-------------------------------------

    Fix Version/s: 4.1.1
       Resolution: Fixed

Patch applied, thanks. 

> Unit tests using JSONObject.toString are fragile & may break in different 
> environments.
> ---------------------------------------------------------------------------------------
>
>                 Key: TAPESTRY-1028
>                 URL: http://issues.apache.org/jira/browse/TAPESTRY-1028
>             Project: Tapestry
>          Issue Type: Bug
>    Affects Versions: 4.1
>         Environment: Windows XP,  JDK 1.5.0_06
>            Reporter: Ben Sommerville
>         Assigned To: Jesse Kuhnert
>            Priority: Minor
>             Fix For: 4.1.1
>
>         Attachments: TAP-1028.patch
>
>
> JSONObject.toString writes out its contents by iterating thru the keys of its 
> internal HashMap.  However the HashMap class makes no guarantees about the 
> ordering of iterators, so the keys + values may be written out in any order.
> The trouble is that the unit tests compare JSONObject.toString to hardcoded 
> strings.  If the iteration order happens to match the test string then all is 
> well.  If it doesn't match then the tests fail, even tho the functionality 
> being tested is working correctly.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: 
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to