Here’s a sneak preview of Miko Matsumura’s and mine presentation concerning Wicket on JavaOne 2005. Of course we will show you what makes Wicket tick, but in the process we will create this application:
And in a matter of minutes transform it into this application:
Pretty cool, ain’t it? Adding delete functionality and paging of a list view without time to blink your eyes seems to me like a nice feature.
This week has multiple goals: preparing for my Wicket presentation on JavaOne 2005 in San Fransisco. Writing an article, more actively looking at the Wicket mailing lists as Eelco is in the Denver mountains (how will he survive without WIFI?) and accompanying demo application and just plain old work in .Net.
The article is coming along just fine: I’m aiming not to write the obiquous ‘Hello, World’ type of article, as we already have a nice example of this on our website, but to show how one creates custom, rich, high level components. The application won’t show any persistency stuff, as it will take too much time to introduce Wicket, show component development and show some persistency related stuff. That may become yet another article, if this one turns out ok.
I’m visiting the greek island of Kos the coming week and even though I’m taking my laptop with me, I doubt I will be spending much time working on Wicket. I am confident that we won’t have too much trouble with our 1.0 release done last tuesday, as there are plenty of people already downloading it.
I hope to return really relaxed and well prepared for my JavaOne 2005 Wicket presentation. I’m taking Wicket 1.0, Tapestry 3.0 and Spring 1.2.1 with me, just in case the weather will turn out to be bad. 
Technorati Tags: wicket
As we are all waiting for the final release of Wicket 1.0 (I know I am), the latest scoop is that Wicket is finalized and is undergoing the final quality checks.
Expect the release to be publicly available on tuesday morning.
While building the final 1.0 release for Wicket I needed to see whether all projects use the same version of the Wicket libraries. Using the Maven multiproject plugin I am able to quickly see whether the projects are using the same version of each library.
First you need to check out the projects you want to check into the same workspace:
wicket/ wicket-extensions/ wicket-examples/ wicket-contrib-data/ wicket-contrib-hibernate2/ wicket-contrib-hibernate3/
Then create in the root directory of the workspace two files: project.xml and project.properties. The project.xml file contains the following:
maven-multiproject-plugin
Note that this is not a complete, nor a valid project.xml for serious development using maven.
The project.properties file contains the following properties:
maven.multiproject.basedir=. maven.multiproject.includes=*/project.xml
Now all you need to do is to run:
maven site
in the workspace root folder where you saved the two Maven project files. The resulting report can then be found in the subdirectory: target/docs/dependency-convergence-report.html.
This is one of the gems why I really like Maven as a project management tool.