[
https://issues.apache.org/jira/browse/WICKET-2756?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Igor Vaynberg resolved WICKET-2756.
-----------------------------------
Resolution: Won't Fix
Assignee: Igor Vaynberg
wicket doesnt use any special serialization mechanisms, only what java
provides. therefore, the standard java rules and restrictions apply, nothing
special. perhaps you are modifying your list from inside a method that
overrides java's standard serialization mechanism.
> ConcurrentModificationException while serializing a page
> --------------------------------------------------------
>
> Key: WICKET-2756
> URL: https://issues.apache.org/jira/browse/WICKET-2756
> Project: Wicket
> Issue Type: Bug
> Components: wicket
> Affects Versions: 1.3.7
> Reporter: Hans Bausewein
> Assignee: Igor Vaynberg
> Attachments: concurrentmodificationstacktrace.txt
>
> Original Estimate: 4h
> Remaining Estimate: 4h
>
> The ConcurrentModificationException could be due to some change in my
> implementation of the Page, while it was being serialized.
> I'd like to report it here, though, because it is an issue with the model
> that Wicket uses.
> I'd recommend to update the documentation with some restrictions on what can
> be in pages.
> Preferably use only immutable objects, no weak references or anything that
> could possibly be changed.
> It's quite difficult to find out what was changing which object, here.
> According to the stack trace the length of a list changed.
> I have checked the logs of the past half year and have not found a single
> other case with the same signature.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
