How-to guides
Directions for a specific goal.
- Keep a page stateless Build a page that Wicket does not store in the session, find the component that makes it stateful, and guard it with a test.
- Configure the page store Change how much page history Wicket keeps per session and where, encrypt stored pages, or replace the disk store with another store.
- Keep data in the session Store per-user data in a typed Wicket session, in session attributes or as metadata, control when the session is created, and end it on logout.
Explanation
Why Wicket works the way it does.
- Stateful and stateless pages Why Wicket keeps pages between requests, how page versions serve the back button, and what a stateless page gives up and gains.
- How pages are stored How Wicket finds the page for a request, and the chain of stores that keeps stateful pages in the request, the session and on disk.