true, it's not 100% stateless :)removing configurable items per page would make 
it stateless.

On 08/08/2011 07:01 PM, jcgarciam wrote:
Just for the record, using HttpSession makes your application already
stateful as well.

On Mon, Aug 8, 2011 at 10:21 AM, Vytautas Racelis-2 [via Apache Wicket]<>  wrote:

  I guess you might be interested in this:

it's a bookmarkable navigator example with abitility to change items per
page and it is stateless.

On Mon, Aug 8, 2011 at 4:16 PM, heikki<[hidden 


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

remembered on the server, but we still have good old HttpSession that
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

To unsubscribe, e-mail: [hidden 
For additional commands, e-mail: [hidden 

Best regards,
Vytautas R.

  If you reply to this email, your message will be added to the discussion
  To start a new topic under Apache Wicket, email
To unsubscribe from Apache Wicket, click 


To unsubscribe, e-mail:
For additional commands, e-mail:

Reply via email to