What design decisions were made regarding state management?
There are probably only a small percentage (perhaps 20%-30%) of all web applications written that have to scale up to large clusters of machines with hundreds of concurrent users. Unfortunately, many web application frameworks are built around the assumption that everyone wants to build web applications of this size. The result being that people with the skills and resources available to build such applications are happy, while the other 80% of people are forced to jump through many hoops and do loads of manual state management that is not really necessary for the size of application they are building. Wicket adopts an alternative approach. What we have tried to do is build a framework where out of the box (and for perhaps 50%+) of applications the developers do not need to worry about state management at all. No need to directly access the session, no need to enlist the help of second level caches or to manually reconstruct object state for each request and so on. Application develope
