I'm not convinced this is a good solution, but I'm concerned that most people are ignoring this problem. I love everything about wicket, except this. In this regard, wicket is a giant step backwards from other frameworks like webwork, struts, etc.
Most struts-like apps that I've seen had problems like this too, at least for parts of the application. Theoretically, there's no need to have such problems, but practically, programmers depend on ad-hoc session state a lot to keep track of things like the current tab/ wizard step and e.g. pagination number in pageable lists. You can acchieve almost the same with Wicket by using stateless bookmarkable pages for everything. But if you really want to program like that, there are probably better frameworks to use. Eelco ------------------------------------------------------- Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnk&kid0709&bid&3057&dat1642 _______________________________________________ Wicket-user mailing list Wicket-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wicket-user
