org.apache.wicket.package.html Maven / Gradle / Ivy

Go to download

Show more of this group Show more artifacts with this name
Show all versions of wicket-core Show documentation

Wicket is a Java web application framework that takes simplicity, separation of concerns and ease of development to a whole new level. Wicket pages can be mocked up, previewed and later revised using standard WYSIWYG HTML design tools. Dynamic content processing and form handling is all handled in Java code using a first-class component model backed by POJO data beans that can easily be persisted using your favorite technology.

The newest version!





wicket package



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

	{@link org.apache.wicket.Application} / {@link org.apache.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 org.apache.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 org.apache.wicket.request.cycle.IRequestCycleListener} - If you are working with a persistence framework
	such as Hibernate or JDO, you may need to implement a request cycle listener in order
	to open a persistence session at the beginning of a request and close the session
	at the end of the request.

	
{@link org.apache.wicket.MarkupContainer} - You will need to study MarkupContainer carefully as
	this class contains all the logic for creating and maintaining component hierarchies.
	
	
{@link org.apache.wicket.Page} / {@link org.apache.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 org.apache.wicket.request.mapper.parameter.PageParameters} - A simple wrapper for query string parameters.
	
	
{@link org.apache.wicket.Session} / {@link org.apache.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.