no its not possible there is logic that ties the return call of size() to a
few things that need to happen before the call to iterator()
all it takes is your own subclass that i have shown you, i dont think its a
big deal.
-igor
On 12/5/06, Manuel Barzi <[EMAIL PROTECTED]> wrote:
My question is, nevertheless, would it be a significant implementation
change to swap calls order from to current to iterator(...) first and
size() later? then adding support for both cases in a
SortableDataProvider (Case 1: Big databases - 2 Calls, Case 2: Small
databases - 1 Call)...
>From my point of view, if supporting both cases, just by swapping
those method calls (if so easy is it...), then it would be great, no
worries to look for another impl... all-in-one...
Just wondering... ;)
Thank you for all your answers...
-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share
your
opinions on IT & business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
Wicket-user mailing list
Wicket-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wicket-user
-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
Wicket-user mailing list
Wicket-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wicket-user
