QA InfoTech » Company » WICKET in Nut·Shell

WICKET in Nut·Shell

Whenever we heard of Wicket first thing that come to mind is exciting game of cricket,loud scream of “Howzat”,a brilliant ball by Shane Warne,a great catch by Jonty Rhodes,an excellent batting display by Sachin Tendulkar and so many excitement surrounding it ,wait a second this is not a blog about cricket ;-),well then I must say Wicket is no longer a property of cricket alone,not any more.

Apache Wicket usually referred as Wicket is a very versatile.lightweight,component based web application framework for JAVA Developers.If we have to explain wicket in one line we can simply say,it is a stateful framework in which we simply program in JAVA,HTML with meaningful abstractions and it bridges the gap between stateless HTTP and stateful Object Oriented Programming.

Wicket Architecture

Wicket Filter

All the requests come to Wicket Filter , as the name suggest it filters the request and process only the wicket requests,rest of the requests are passed on to the chain.As a result resources outside the scope of Wicket Application,(for e.g:Static contents such as css, js files etc) will be served by the container.

Application

This is the main entry point of any wicket base application.One can have only one instance of it per application.We can customize various settings, addition of resources etc in this phase.

Components

This are the main bricks of any wicket application.Wicket has large set of components such as TextField,TextArea,Label, Form etc.

Model

Model binds data with wicket component i.e it holds the data for wicket component.Data hiding is implemented through model.Many types of model are available in wicket such as Static Model,Dynamic Model,Property model, Abstract ReadOnly Model,Loadable Detachable Model etc.

Request Cycle

This is responsible for handling all requests whether stateful or stateless.

It constitute of following steps

  •  Decode Request
  •  Determine Request Target
  •  Process Events
  •  Respond

Behaviors

We can think of behavior as a plug-ins for component that allow various functionality to be added to the component and get events forwarded by component.

In conclusion we can say since wicket is a component based framework so it is quite easy to understand and  no xml configuration is required for wicket application so all can be done using java code,which is a great relief.

About the Author