Tony, Without seeing the code, I would first try overriding onPopulate, calling removeAll and then probably super.onPopulate.
If that starts getting a bit hairy, I think that Timo's idea (use RefreshingView) is probably more sensible anyway, unless there is a special reason you chose to use a ListView. If all of that fails, send me a quickstart ( http://www.jweekend.co.uk/dev/ContactUsBody/ drop me a line and I'll send you my email address) and I'll try to take look, hopefully by tomorrow evening (GMT), partly because I'm a bit curious at how the state is getting so muddled. Regards - Cemal http://jWeekend.co.uk tfu wrote: > > Cemal, > > I'm not sure where/how to force a ListView removeAll() in my case. > Overriding the Ajax timer behavior? > > I agree the problem could be that the underlying model for the ListView is > changed before it is rendered completely. So, the real solution is to > prevent this from happening. Synchronization? Where? How? > > Regards, > Tony > > > > jWeekend wrote: >> >> Tony, >> >> On your ListView, try setReuseItems(true) and force a removeAll() ... Any >> different? >> It's seems like the number of elements in your ListView's model object >> (the ArrayList mentioned in the stack trace) has changed (been reduced) >> by the time the WMC is refreshed, and then the new "size" no longer >> matches some stale "size". >> >> Regards - Cemal >> http://www.jWeekend.co.uk http://jWeekend.co.uk >> > > -- View this message in context: http://www.nabble.com/Help-needed---ListView.onPopulate-IndexOutOfBoundsException-tp19058649p19076094.html Sent from the Wicket - User mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
