> The problem is that if the user's session times out while they are looking > at the search page, we lose the form state in wicket, and so the form posts > for various inputs will fail. (This seems to apply to both ajax posts and > regular submits, though most of our state updates are ajaxy...)
For regular posts, there is a way out of this: stateless pages with stateless forms. For Ajax calls there isn't currently. I'm still advocating that, but we're not sure how that would work best yet. Concrete ideas are welcome. Johan, maybe you could state your objections or difficulties with that here so that we can discuss further? Also, submitting to bookmarkable pages is possible anyway, as the urls are constructed using a 'public' pattern, and if you use url mounting that'll even be easier. If you want to do a form post to a bookmarkable page, you have to write the action attribute yourself and you have to get the parameters from the page parameters argument in the constructor. But doing that would greatly corrupt the advantages of working with Wicket, so I'd like to propose you try working with stateless pages/ forms first. Eelco ------------------------------------------------------------------------- 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 [email protected] https://lists.sourceforge.net/lists/listinfo/wicket-user
