Some of the components require you to pass in a list of objects to page through (ListView for example). Others, like DataTable, etc., let you use an IDataProvider instance which allows you to let the database do the paging. Take a look at my StudentDataProvider implementation (an inner class):
http://svn.carmanconsulting.com/public/wicket-advanced/trunk/src/main/java/com/carmanconsulting/wicket/advanced/web/story3/page/Home.java On Wed, Jul 23, 2008 at 6:44 PM, ej595 <[EMAIL PROTECTED]> wrote: > > Hi all, > im from a JSF background and so far ive been really impressed with what ive > seen on the Wicket side of things. Im a little confused on the pagable > lists, pagable datatables, ajax navigators etc. It seems that when > retrieving records, the 'paging' is more client-side. By that i mean it they > load the ENTIRE query contents and page though a list - this is fine when > dealing with very few number of records, however my app will potentially > return 1,000 of records which is impractical if you then scale that by 100s > of users. Is there a way to get these 'pagable' components to retrieve from > the DB a pageful or records at a time as opposed to the entire search > results. So, if ive sent the max page display to 10, and want to retreive > the next 10, then its another call to the DB and not simply a arraylist - > subList(from, to) ?? > > > I hope this is reasonably clear. > -- > View this message in context: > http://www.nabble.com/PageableListView-%2B-AJax-and-loading-DB-contents-tp18622171p18622171.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] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
