Chapter 1. What is Wicket?
Figure 1.1. A cricket wicket: a set of three stumps topped by bails. This isn’t the topic of this book.
Figure 1.2. Google search results for wicket. The number one result has nothing to do with cricket or with the furry and highly dangerous inhabitants of Endor.
Figure 1.3. A request/response pair for a JSP-based application
Figure 1.4. A Model 2 framework lets the controllers decide what views to render.
Figure 1.5. An example of a web application. This figure shows a screen from Teachscape, a learning-management application used by school districts throughout the United States.
Figure 1.6. The web application after the Components Available to Members tab is clicked
Figure 1.7. The Hello World! example as rendered in a browser window
Figure 1.8. Lining up the component in the markup file and Java class
Figure 1.9. The link example shows a link that increases the value of a counter with each click.
Figure 1.10. This example echoes the text in the input field on the page.
Chapter 2. The architecture of Wicket
Figure 2.1. One application handles multiple sessions, each of which handles multiple requests over its lifetime.
Figure 2.2. Important classes for handling requests. The Application class is responsible for the instantiation of most objects.
Figure 2.3. The conceptual relationship between session stores, sessions, page maps, and pages