not sure I understand the reasoning for the deprecation.
use PaginatedList when I want to display a list of rows a page at a time.
I keep the list in the session, and call nextPage() and previousPage() based on
events. Since the list is already handling reading extra data, it's very
responsive. When I'm done with the list, I discard it.
don't see why it's not flexible if PaginatedList is the interface. Can't
someone still write to this interface?
PaginatedList provides a wrapper around the queryForList() method - it's
calling it in the getList method, so if it's using it
think it provides an easy way of dealing with a common web interface
well, just some thoughts. It's not like I'm going to stop using it - it's
I'd like to suggest
that we deprecate the PaginatedList interface, all implementations of it, and
the SqlMapClient methods that use it.
- It's currently overused where it probably shouldn't be used at all.
- It's not a flexible model, so you can't supply your own implementation
- Using queryForList() with skip and count parameters is better all