As per the API: Exception invoked when when stale link has been clicked. The page should then be rerendered with an explanatory error message.
Read more about the Sateless Links http://wicket.apache.org/guide/guide/chapter9.html#chapter9_5 And about Page Versions: http://wicket.apache.org/guide/guide/chapter7.html Or provide us with a quickstart so we can see what's going on. Or the full stack trace at least. On Fri, Jan 3, 2014 at 10:13 AM, eaglei22 <jchojnack...@gmail.com> wrote: > I seem to be able to avoid this by limiting the amount of rows I print to > the > screen from the ListView. I turned it into a PageableListView and put a max > of 200 per page, and the problem went away. > > -- > View this message in context: > http://apache-wicket.1842946.n4.nabble.com/MultiThreading-issues-with-Wicket-tp4663325p4663438.html > Sent from the Users forum mailing list archive at Nabble.com. > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org > For additional commands, e-mail: users-h...@wicket.apache.org > >