You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@wicket.apache.org by "Juergen Donnerstag (JIRA)" <ji...@apache.org> on 2009/10/24 11:51:59 UTC

[jira] Resolved: (WICKET-2526) ConcurrentModification Exception in TreeState

     [ https://issues.apache.org/jira/browse/WICKET-2526?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Juergen Donnerstag resolved WICKET-2526.
----------------------------------------

    Resolution: Invalid
      Assignee: Juergen Donnerstag

Martin is right. The contract is that newXXX should only be subclassed to create your own state and getXXX whenever you feel the need to retrieve it from somewhere else or do something special with it.

> ConcurrentModification Exception in TreeState
> ---------------------------------------------
>
>                 Key: WICKET-2526
>                 URL: https://issues.apache.org/jira/browse/WICKET-2526
>             Project: Wicket
>          Issue Type: Bug
>          Components: wicket
>    Affects Versions: 1.4.2
>            Reporter: count negative
>            Assignee: Juergen Donnerstag
>         Attachments: sessionSet.zip
>
>
> When the TreeState ist saved in the session, pressing F5 (refresh) in browser many times, leds to an ConcurrentModificationException. Example project is submitted.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.