Tag: web technology

Clean separation of concerns between HTML and Java

Automated state management

conjunction with JSP and custom tag libraries

Abstraction away from Servlet API and HTTP protocol details

It is not particularly object-oriented.

You work with hierarchies of components and design your application as such.

Unless you output HTML directly from your Java code you still need to learn another major technology JSP plus custom tag libraries in order to produce output HTML pages.

A very clean object-oriented and component based approach.

Each Action class defines an abstraction, but the abstraction is determined by the HTTP procotol request mechanism rather than by an object-oriented analysis

Wicket is fully object-oriented. You work with hierarchies of components and design your application as such.

Wicket markup files are as close to pure HTML as it is possible to get. Where Wicket does introduce content into the markup it is very clean and complies with all XHTML standards

Wicket is based around intercepting each HTTP request to a web application and directing it to a specific Action class that handles the request

True

False

True

False

True

False

Component based

All framework classes are based on interfaces

Pure Java + Pure HTML

State Management

June,2009

July,2007

June,2007

July,2010

JSP

Servlets

Ajax

Applet

Infrastructure

Global catalogue

PDC

RID