Wicket serializes access to each page instance, but provides no further synchronization. Non-transient references to application data must be synchronized by you.
On Tue, Jul 16, 2013 at 2:39 PM, saty <[email protected]> wrote: > Thanks, but could you please explain how wicket handles serialization of > objects that could throw this error. > I could be wrong but it appears to me wicket is iterating the data > structure > for its serialization efforts when its being modified by other threads as > well and the iteration results in ConcurrentModificationException being > thrown by data structure iterator. > > > > -- > View this message in context: > http://apache-wicket.1842946.n4.nabble.com/How-to-resolve-this-java-util-ConcurrentModificationException-tp4660273p4660296.html > Sent from the Users forum mailing list archive at Nabble.com. > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > >
