However, when I looked in the NetBeans HTTP Monitor (which is displayed by default when you deploy an application over Tomcat), I saw this:
Looking at the HTTP Monitor I knew for the first time that I was missing a stylesheet. So, I went back to Wicket's examples folders and looked for the stylesheet. When you look at the Request URI field in the Request tab in the illustration above, you'll see where the stylesheet was expected to be found. So that's where I put it. Then I re-deployed the application and it displayed correctly in the browser, including the stylesheet. However, this is what I saw in the HTTP Monitor:
So now I knew that a file called wicket-logo.png was missing. So I looked for it in Wicket's examples folders and placed it exactly where the Request URI field in the illustration above told me to. When I deployed the application again, both the stylesheet and the logo were displayed. However, this time when I looked in the HTTP Monitor, I saw the following:
Here I can see that the stylesheet and the logo were found; however, there seems to be some kind of message about the stylesheet. The icon is not red like in the previous records, and in the Request tab I see that the HTTP exit status is "304: Not Modified". "What does this mean?" I asked myself. "Is this a problem or just some kind of information?" So I pressed F1 in the HTTP Monitor. I found this text (click to enlarge):
So I clicked the "Analyzing Session Data" link and found a page that describes what all the icons in the HTTP Monitor mean. It includes a link to the W3.org Status Code Definitions page, which told me that the 304 status code is nothing to be worried about. It is just informational.
In other words, the IDE's HTTP Monitor and its help topics are a really useful combination when working with Wicket. I've never really used the HTTP Monitor extensively before, but will now do so while disentangling Wicket's examples.