Wicket allows the developer to build a page in Java (you remember Java right?
It's like OGNL, but with even more cool features) that uses and manipulates an HTML file, not the other way around.
This page exists across requests, and does not even need to be aware of the request/response cycle.
But something needs to know when a new request is starting and when the last one has finished rendering, right?
Backing classes tends to be a series of listener methods, at the total mercy of the page template that is supposed to be merely defining the placement of components.
This works fine, and it is definitely a step up from a model 2 controller singleton class.
We have only told Wicket where to render the label component in the web page.
In the next section we will show how to tell Wicket to render the message.
As much as the word "template" would seem to suggest otherwise, this makes the page template king.It knows that get Member() is going to be called on every request, and reacts accordingly by getting a fresh copy from the database.Sure, the developer needs to deal with these details, but does it really have to be dealt with at the very top level of the application?Using components allows the developer to spend less time on the visual tier of his or her app and more time implementing the core functionality.Even more important is how extensible this makes component-based GUIs.