I've several statuful pages in five or 6 projects .... Tipical scenario is when i have a searchable list of items from the user.
I use a form to allow user to filter the items in the table. the user can select viewable columns too. Usually we talk about 8 -12 elements plus control for each column. Then the user can click on an item and go to a page where he can edit/mnipulate data .... then he gets back to the page. Having stateful pages is a quick way form me to store navigation information in session, which i find more pratical than passing around as request attribute ( but i'm aware this is quite a personal feeling ). I've been using click from versione 0.19, and i admit i was very happy when Malcolm introduces stateful pages. On other and I've to admit that to managed stateful pages to work properly requires a great deal of insigth on Click pages lifecycle .... which took me a while to reach.... I found Click very found and productive to use, expecially when combined with Cayenne. The only thing i complain it's not lack of visibility of the framework, but maybe there has bees too much changes in the api.... Sometimes it's quite hard to keep the pace :-D in the and my two cents is that i'like to have stateful pages more than not having them... -- Marco
