If you expect to have very big tables then the best approach performance wise is to create your own Table component that creates its markup by concatenating the markup of its children components. For example see the difference between DropDownChoice and Select components in Wicket. Both components provide the same functionality but Select uses a sub component SelectOption for all its options and this makes it more heavy. While DDC just concatenates "<option ...>...</option>"s.
On Fri, Oct 5, 2012 at 6:18 AM, lukuperman <lukuper...@hotmail.com> wrote: > Hi Martin, yes I did some profiling focusing on my classes. I'll post the > results shortly. In the meantime, is there any preference between 2 nested > dataviews vs datatable when table has dynamic number of columns, considering > performance as driver? > > Lucas Kuperman > > > > -- > View this message in context: > http://apache-wicket.1842946.n4.nabble.com/performance-on-nested-dataviews-tp4652673p4652677.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 > -- Martin Grigorov jWeekend Training, Consulting, Development http://jWeekend.com --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
