wicket

The core Wicket package. The key core classes you will need to learn to do basic Wicket programming are:

• {@link wicket.Application} / {@link wicket.protocol.http.WebApplication} - Subclass WebApplication to create your application. Set your home page with Application.getPages().setHomePage(MyHomePage.class). Configure Wicket for deployment with Application.getSettings().configure("deployment"). Substitute "development" to get default settings for a development environment.
• {@link wicket.Component} - You will need to carefully study this class as Component is very central to Wicket. There are a large number of convenience methods in Component and, naturally, every component in Wicket is a subclass of Component, so all these methods are available to all Components.
• {@link wicket.IRequestCycleFactory} - If you are working with a persistence framework such as Hibernate or JDO, you may need to implement a request cycle factory in order to open a persistence session at the beginning of a request and close the session at the end of the request.
• {@link wicket.ISessionFactory} - For all but the most trivial applications, you will need to create your own session factory. Your implementation of this interface will generally be quite simple, generally just returning a new instance of your own application-specific subclass of WebSession.
• {@link wicket.MarkupContainer} - You will need to study MarkupContainer carefully as this class contains all the logic for creating and maintaining component hierarchies.
• {@link wicket.Page} / {@link wicket.markup.html.WebPage} - Every page in your wicket application will extend WebPage (or some other subclass of Page if you are writing something other than a web application). There are a number of important methods in Page and you should be familiar with all of them.
• {@link wicket.PageParameters} - A simple wrapper for query string parameters.
• {@link wicket.Session} / {@link wicket.protocol.http.WebSession} - It is particularly important to understand Session if you are doing clustering, but even for a very basic application you will want to create your own subclass of WebSession using a session factory so that you can store any session properties in a typesafe way. Note that since Pages are first class objects with models of their own, it is likely or at least possible that you will not have many session properties.

• Identity - All Components must have a non-null id which is retrieved by calling getId().

A request target is the base entity that is the subject of a request. Different types of request have different request targets.

• Children - Children can be added by calling the add() method, and they can be looked up using a dotted path.

Represents the request cycle, including the applicable application, page, request, response and session.

Convenient container for an application, session, request and response object for a page request cycle.

Resources themselves do not currently have URLs.

• Access via RequestCycle - The Session for a RequestCycle can be retrieved by calling RequestCycle.getSession .
• Access via Component - If a RequestCycle object is not available, the Session can be retrieved for a Component by calling Component.getSession .