Tutorials
Lessons that build something that works, step by step.
- Build your first application Generate a project from the quickstart, run it, and build a home page with a label, a click counter and a link to a second page.
- Give every page the same layout Move the header, navigation and footer of your application into a base page and two panels, so every page shares one layout.
- Build a form that saves data Add a guestbook page with a form that validates its input, saves entries and lists them, and shows errors and a confirmation.
- Update a page with Ajax Make the click counter and the guestbook form update only the parts of the page that change, open the form without a reload, and refresh the guestbook every ten seconds.
- Test a page with WicketTester Write JUnit tests that render your pages, click links, submit the guestbook form and check Ajax updates, without a browser or a server.
How-to guides
Directions for a specific goal.
- Create a project from the quickstart archetype Generate a ready-to-run Wicket project with Maven, know what is in it, and open it in your IDE.
- Switch between development and deployment mode Run Wicket in deployment mode on production servers, with a system property, a web.xml parameter or code, and check which mode is active.
Reference
The classes, tags and settings, described.
- Wicket modules The artifacts Wicket is released as, what each one contains, which Wicket modules it depends on, and which you need for testing and tooling.
- Maven dependencies The Maven dependencies, versions, scopes and build settings a Wicket project needs, for Wicket 10 and Wicket 11.
- Application settings How a Wicket application is started and configured, the settings objects with their main options and defaults, and what development and deployment mode change.
- Glossary Plain-English definitions of the Wicket terms used in this guide, each compared with what other web frameworks call it.
Explanation
Why Wicket works the way it does.
- Why component-oriented What a component-oriented framework does differently from request-based MVC frameworks, what Wicket gains from it, and what it costs.
- Best practices The habits that keep a Wicket application easy to change and to test, each with the reason it follows from how Wicket works.