Hi, I've been using the DefaultDataTable component in Wicket which allow me to paginate through a few pages worth of multi column data.
I believe the general approach is to load all data from the database into the session first (as a List of Domain Objects ?), then as navigation links are clicked show subsets of this list? I'm using Spring Beans Injection to inject the Data Access Object into a subclass of SortableDataProvider (called QueryDataProvider). Then within the QueryDataProviders constructor I'm calling a method in the DataAccessObject to create the List of Data Objects. The DataProvider's iterator method then calls a subset of the List stored in the DataAccessObject. I'm pretty sure this is an awful way of designing my data access, if I click the nav links just a bit too fast I get the following error: WicketMessage: After 1 minute the Pagemap null is still locked by: Thread[http-8080-1,5,main], giving up trying to get the page for path: 16:entries:topToolbars:1:toolbar:span:navigator:navigation:1:pageLink How should I be doing things differently? Thanks for any help, much appreciated. Will -- View this message in context: http://www.nabble.com/Data-Access-Design-for-Pagination-tp17404681p17404681.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]
