. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37 7. Components lifecycle . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 117 12.9. Creating complex form components with FormComponentPanel. . . . . . . . . . . . . . . . . . . . . . . 119 12.10. Stateless form 143 14.2. Improved auto components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 147 14.3. When are components dequeued? . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37 7. Components lifecycle . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 113 12.9. Creating complex form components with FormComponentPanel. . . . . . . . . . . . . . . . . . . . . . . 115 12.10. Stateless form 137 14.2. Improved auto components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 140 14.3. When are components dequeued? . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36 7. Components lifecycle . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 112 12.9. Creating complex form components with FormComponentPanel. . . . . . . . . . . . . . . . . . . . . . . 114 12.10. Stateless form 136 14.2. Improved auto components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 139 14.3. When are components dequeued? . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37 7. Components lifecycle . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 116 12.9. Creating complex form components with FormComponentPanel. . . . . . . . . . . . . . . . . . . . . . . 118 12.10. Stateless form 142 14.2. Improved auto components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 146 14.3. When are components dequeued? . . . . . .

LoginForm and LoginFormRevisited. ● With this kind of framework our web pages and their HTML components (forms, input controls, links, etc...), are pure class instances. Since pages are class instances is very similar to what GUI frameworks (like Swing or SWT) do with desktop windows and their components. Wicket and the other component oriented frameworks bring to web development the same kind of stateless nature. Component oriented framework ● Wicket allows us to design our web pages in terms of components and containers, just like AWT does with desktop windows. Both frameworks share the same component-based