I've noticed that rather many Wicket components cause the page to become
stateful, something which I wish to avoid.

In particular I'm wondering if there is some way to use the Pagination*
components (or similar alternative ones) to create a page that has
pagination over a repeater, without making the page stateful.

Sure, I suppose some info about the collection and current page etc. must be
remembered on the server, but we still have good old HttpSession that could
maybe be used for it ?

Any hints appreciated !

thanks and kind regards
Heikki Doeleman

View this message in context: 
Sent from the Users forum mailing list archive at Nabble.com.

To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org

Reply via email to