Be aware, however, that some mecanism exists to redirect the user to some peculiar page and then back to the previous one.It's commonly and easily used to deal with user login and may be part, one day, of another article.You could now to whatever html fancy stuff of your wish, as long as the wicket:id are here and the main model hierarchy respected, it will work.You may notice as well that the button has no wicket:id.The form has been directly added to the page, and the textarea to the form whom it belongs to.Each component has been given its wicket:id found in the page.This tutorial is designed as a "first hands on Wicket" one.
Oh, for sure, it's a fairly basic one, with only one page. I called my project tutorial from the organisation org.zedros. First of all, we find the Wicket framework itself, as well as a sample application and an embedded webserver called Jetty. In the org.zedros package, you can easily spot some peculiar files : As with any Java website, another important file is the one. When looking at it, you can see that Wicket uses a filter instead of the usual servlet.
If needed, one can easily drop a question and get an answer really fast.
In fact, most of the Wicket core developers are on it, so the answers are really first class ones.
It should pick up the file, which contains the main class. Then go on " and you should see something like that : We agree that the look of this page is pretty basic.
But it's just some simple html file : you're free to do whatever you want in it, just go for it.
A few others Wicket attributes exist as well, but overall your page will always stay close from an html one.