On 9/7/05, Eelco Hillenius <[EMAIL PROTECTED]> wrote: > I'm a bit short in time currently, so I haven't taken a very detailed > look at your proposal. However, my first question is why you want to > use bookmarkable pages at all?
Um, because I do not want to create a new instance of bookmarkable page each time I access it? Because I want to see the same data on the form as I entered earlier? SignIn example uses bookmarkable pages, so I worked with them. > If you want to preserve state, the way > to go would be to use links and forms. I did not quite get this. > It looks to me you're looking for a zero state mechanism here. For > that, there's too much at stake to implement a quick resolution. It > (the research at least) is scheduled for 1.2, and will have > consequences for many Wicket internals. Zero-state meaning _viewstate-like request parameter? No, I did not mean that. Quite contrary, I hate _viewstate approach. All I want is to reuse instances of Pages (or at least of their models). Michael. ------------------------------------------------------- SF.Net email is Sponsored by the Better Software Conference & EXPO September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf _______________________________________________ Wicket-develop mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/wicket-develop
