Ajaxformcomponentupdatingbehavior wicket 1 4
Now we are ready to build our first Wicket application.
Let’s start by subclassing Wicket’s Wicket favors convention over configuration.
In the example, it is the Hello that corresponds with Hello
Note: You must ensure that the actual HTML file and the page class name are the same (for example, Hello and Hello World.java) and that both are in the same place on the CLASSPATH.
Instead of creating a controller or action class, you create a page, place components on it, and define how each component reacts to user input.
To truly demonstrate the simplicity of developing Web-based applications using Wicket, you'll start by developing a simple "Hello World" example.
In this article, we will introduce the basics by building the You may want to check out the latest version of Wicket in the Maven Central repository, which at the time of your reading may not coincide with the one used here.
By taking away this task, Wicket allows you to concentrate on the application's business logic.
As a Wicket developer, you should think in terms of building reusable components that are stateful, instead of building controllers that handle request/response objects and worrying about multithreading issues.
Like other frameworks, Wicket is built on top of Sun Microsystems' servlet API.
However, unlike frameworks based on the Model-View-Controller (MVC) model (such as Struts), Wicket takes away from you the task of handling request/response objects, which is inherent with technologies such as servlets.