However, to get it running right from the start, the jetty webserver is embedded as well. Thus you can directly launch and use the sample application, without the burden of having to install a webserver. This allows a more fine grained way of telling which paths are part of the web application, allowing to put multiple kind of files on the same webserver even if some of them aren't managed by Wicket.
Furthermore, the turnaround time (time of restart) of Jetty is pretty low (I had read that it was among the shortest... It's all you need to have your first Wicket application running !
Read further for a tutorial exploring possibilities to improve the location of the error on the page, thereby improving usability.
The default Feedback Panel shows all errors in one place.
To make it attractive and pertinent in regard of Wicket capacities, we'll do a "Wicket and Ajax enabled autosaved textfield". The Quickstart project is an already setup Wicket website. The website being in English, as the current text, I won't put here the installation info found on the website. Just a last point : I did this tutorial using Eclipse 3.3, so you're better off opening the project with Eclipse.
In my opinion, declarative approach of JSF is less verbose.The result is cleaner HTML, but messier Java code with an inner class.Personally, I don't like having many inner classes because I find it difficult to read.By default Wicket shows error messages together in a single place in the HTML form.This has some drawbacks to usability, especially if you have long forms with lots of fields.