Wicket is congealing into 1.2 pretty quickly now. The latest release didn’t break anything in Databinder or its examples. Even so, I’m marking the occasion with an updated Databinder snapshot.

This time I worked on making nice in all ways with 1.2, starting with recognition of wicket.configuration for specifying “deployment” mode. (The old way will still work, for now.)

I also remembered that Wicket has incorporated my own PropertyListView so there’s no longer any reason to keep it in Databinder. The class is now deprecated, and its still-useful move up/down & remove inner classes have been pulled into independent classes.

Lastly, I made a change to fully initialize Databinder applications on startup. Previously, the Hibernate session factory was constructed in a static block of DataRequestCycle that wouldn’t execute until the first request. I converted that block into a static method called from DataApplication.init(). This way the ten second table processing delay can happen while you’re checking your e-mail (or whatever it is you do after telling a Java app server to start up).

Go an’ get ’em: Databinder snapshot and Wicket 1.2 rc1.

By the way, I do share Locke’s sentiment that Wicket is about to become wildly popular. But I’m a little creeped out by that first comment, as I did just see the original Stepford Wives. Guess the next remake should be set in Belgium…