> > > Etc. There's a ton more questions to ask, but I'm sure you'll figure > that out in the context of your project :-) One of the most important > decisions you'll make is what parts of your application (maybe even > everything) you'll set up to be stateless and bookmarkable. Keep in > mind that even though Wicket is stateful by default, you can build an > entire app in a stateless fashion. The drawback to that is that you'll > lose some of the OO programming model, but it might still be a nicer > programming model than you'd have with many of the model 2 frameworks. > Or you can make a mix, like a stateless section for anonymous users > and stateful for logged in users. > > Eelco >
I wouldn't sell wicket short here. Yes, the Stateful Wicket programming model is *extremely* elegant, but the Stateless Wicket programming model is still the BEST around. Hands down... =)
