since this is rare, wouldn't it be better for people in those cases to just create a list, sublist or specialized list implementation?
Donnerstag, Juergen wrote:
In some very rare cases you might want to break the iteration while
rendering all ListItems of a ListView. I'm not sure which approach is the
best one.
A) populateItem() and renderItem() to return a boolean value. False = break the loop B) ListView implementing a method stopRender(). Arriving at the next checkpoint (there would be two), handleRender will check the value and break the loop. C) A ListItemException. If thrown you break the loop, but nothing else happens. No error.
What is your advice?
Regards Juergen
-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now. http://productguide.itmanagersjournal.com/
_______________________________________________
Wicket-develop mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/wicket-develop
-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now. http://productguide.itmanagersjournal.com/
_______________________________________________
Wicket-develop mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/wicket-develop
