You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@wicket.apache.org by "Martin Grigorov (JIRA)" <ji...@apache.org> on 2012/10/01 17:03:07 UTC
[jira] [Commented] (WICKET-4795) Wicket unit tests rely on hashmap
iteration order
[ https://issues.apache.org/jira/browse/WICKET-4795?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13466862#comment-13466862 ]
Martin Grigorov commented on WICKET-4795:
-----------------------------------------
Can you give an example of a failing test ?
And please paste the produced exception.
Thanks!
> Wicket unit tests rely on hashmap iteration order
> -------------------------------------------------
>
> Key: WICKET-4795
> URL: https://issues.apache.org/jira/browse/WICKET-4795
> Project: Wicket
> Issue Type: Bug
> Components: wicket
> Affects Versions: 1.4.21, 1.5.8, 6.0.0
> Reporter: Mikko Tiihonen
> Attachments: fix-WICKET-4795.patch
>
>
> Starting from version 7u5 java has supported randomizing the hashmap String key order (enabling this will fix CVE-2012-2739). It is also a good way to test the code if it is relying on hashmap order.
> More details: http://docs.oracle.com/javase/7/docs/technotes/guides/collections/changes7.html
> In the latest Java 8 (b58) the randomized hashmap is enabled by default causing some wicket unit tests to fail randomly.
--
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