> No, the query cache only caches the primary keys... This sounds exactly like iterate() but you have to remember to call setCachable(true).
> One thing I would add though, would be a setPageableListView() method. > If the DataProvider knows about its container, it can do > cleanup things when it's underlying data changes (like a > removeAll() when a sort order or filter is added). I was thinking of having iterator(int first, int count, DataView dataView) which would eliminate the requirement for keeping state in the dataprovider and still let you work directly off the interface. Currently I call removeAll() every request, your data can change at any point w/out you knowing (new row gets inserted that would be in the middle of listview). This can be fixed by letting the user override the id for the listitem - setting it to the pk of the object. That way we can keep a list of listitems not rendered during the request and delete them at the end. Does this sound like it would work? If so I will implement it. Igor ------------------------------------------------------- SF.Net email is sponsored by: Discover Easy Linux Migration Strategies from IBM. Find simple to follow Roadmaps, straightforward articles, informative Webcasts and more! Get everything you need to get up to speed, fast. http://ads.osdn.com/?ad_id=7477&alloc_id=16492&op=click _______________________________________________ Wicket-user mailing list Wicket-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wicket-user
