> Why would want to cache the result? Look, you have to make a decission. Are you interested in paging lists or not? If you are, you should do a count query to determine how many rows there are, and then just load the page of results you need with another one. If you don't want to use paging, but you want to display the whole result set at once, Timo's answer will work fine.
> what happened if the results returned are big If the results can be big, use a pageable list. It's the whole point of the constructs we have that these components will load just what is needed instead of all the results. Eelco ------------------------------------------------------------------------- This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/ _______________________________________________ Wicket-user mailing list Wicket-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wicket-user
