Recent Posts by Geertjan Wielenga

In Log4j, Wicket, Tomcat, and NetBeans IDE, I took my first tentative steps in the land of Log4j. Today I found that someone had left a comment at the end of that blog entry, telling me about something I hadn't heard of yet (which is further evidence of the usefulness of blogging) -- a handy GUI that displays all the Log4j messages in NetBeans IDE: Lumbermill plug-in for NetBeans. It's really really really very cool. Really. Here's a screenshot of what it looked like for...

I've converted the Wicket Examples into NetBeans IDE projects. This means that you don't need to build the samples from scratch -- you can just download the ZIP file and open the samples as projects in NetBeans IDE 4.1. Once everything's set up and running smoothly, you can look at the source and learn how everything works. Do the following to get going with Wicket in NetBeans IDE 4.1: Download the resources. Wicket API. NetBeans IDE 4.1. NetBeans projectized Wicket samples....

I'm really enjoying Wicket and what seems to me to be a very simple approach to web application development. There's no better way to get to learn a technology than to look at its examples, and this is what I've been doing -- because, fortunately, Wicket has a lot of examples. And they're really very useful. However, less fortunately, some of them seem to be intertwined with each other so that one example depends on another. I prefer learning about a technology by studying...

I've been trying to get my head around Wicket, a relatively new Web framework. (Here's one of several articles about it.) And this is some information on "NavoMatic", the example I've been using to learn about Wicket: Demonstration Code and analysis Of course, I'm using NetBeans IDE to code and deploy the application. Here's what my Projects window looked like after everything was working as expected: Now that everything's up and running, I can have a closer look at everything...

I'm getting acquainted with Wicket (which I blogged about here). In doing so, I encountered some problems and got a few responses from Wicket's mailing list. Someone suggested that I use Log4j to debug my issues, and so -- for the first time -- I used Log4j today. So here, as a reminder to myself and possibly of benefit to others, is what I did to use Log4j for debugging a Wicket application deployed over Tomcat from NetBeans IDE:Stop the running Tomcat instance. (In the...

In previous blog entries, and in the new NetBeans File Template Plug-in Tutorial, I describe how to create a branded file template. The file template is branded with the Sun Microsystems copyright text. However, I've just discovered a different way of branding a file. It's not the most efficient way of doing so, but it's fun because it's different. Maybe it will give you some ideas of doing other similar things. There are really only two steps to this process (which...

Embedding a component in the IDE is something I've discussed in a few blog entries a while ago. Now there's also a tutorial available. You start with the Anagram sample, which is the standard J2SE sample that is shipped with the IDE. (To have a look at it, press Ctrl-Shift-N, expand Samples, then General, and then select Anagram Sample. Click Next and then Finish.) During the tutorial, you learn about a few of the NetBeans APIs and you acquaint yourself with the new GUI...

Recently I reported I'd completed a tutorial describing the creation, installation, and sharing of NetBeans IDE file templates. At the end of the tutorial, the New File wizard includes a new template category and template type, as shown below: I've received several comments from various people and now have a 2nd draft of the tutorial available. Here it is: NetBeans File Template Plug-in Tutorial. If you're interested in giving this tutorial a quick review, all you've got to...

I've made some progress in understanding how file templates work. The most interesting thing so far was discovering, yesterday, how to sequence categories in the New File wizard. I applied the same principle today while creating the basis for file templates for each of the test cases supported by Cactus. By default, file templates are listed alphabetically. This means that in the screenshot below, the "Java Package" template should come above the "Servlet Test Case"...