On Apr 29, 2006, at 12:41 PM, Eelco Hillenius wrote:
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.
Yes, but that's the application's fault. At least the developers had
a choice to do things differently (correctly). In those cases, you
could (and probably should) use request parameters instead of session.
You can acchieve almost the same with Wicket by using stateless
bookmarkable pages for everything.
I think forms present the most significant problem, and you can't
have stateless pages when using forms.
But if you really want to program like that, there are probably
better frameworks to use.
For the record, I don't know of any other web frameworks that don't
make me want to shoot myself a few hours into development.
-------------------------------------------------------
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&kid=120709&bid=263057&dat=121642
_______________________________________________
Wicket-user mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/wicket-user
