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
--
View this message in context:
http://www.nabble.com/Help-needed---ListView.onPopulate-IndexOutOfBoundsException-tp19058649p19076746.html
Sent from the Wicket - User mailing list archive at Nabble.com.
-
To unsubscribe, e-mail
this message in context:
http://www.nabble.com/Help-needed---ListView.onPopulate-IndexOutOfBoundsException-tp19058649p19058649.html
Sent from the Wicket - User mailing list archive at Nabble.com.
-
To unsubscribe, e-mail: [EMAIL
(MarkupContainer.java:1577)
... 29 more
Any feedback is highly appreciated
--
View this message in context:
http://www.nabble.com/Help-needed---ListView.onPopulate-IndexOutOfBoundsException-tp19058649p19059616.html
Sent from the Wicket - User mailing list archive at Nabble.com
)
at
org.apache.wicket.MarkupContainer.onBeforeRenderChildren(MarkupContainer.java:1577)
... 29 more
Any feedback is highly appreciated
--
View this message in context:
http://www.nabble.com/Help-needed---ListView.onPopulate-IndexOutOfBoundsException-tp19058649p19059966.html
) 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-tp19058649p19060689
On Tue, 19 Aug 2008, tfu wrote:
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?
It sounds like you could be better off using a more dynamic
