I read Matt's entry on Why Wicket Looks Cool and thought I would give it a go myself. I actually haven't even heard about Wicket until today. My very first thought was "Man, this looks like a Tapestry clone". And while Wicket and Tapestry are very similar, there are noticable differences. For example, and the most notably, all the component decalarations and definitions seem to be done inside a java class instead of Tapestry's .page XML files. That's not the only difference mind you but I haven't looked at it long enough to really get into any other specifics.

It seems solid and performance was good for the few small test apps I created. The biggest problem is, of course, documentation, as Matt stated. I understand that documentation is a work in progress and there are book *talks* but nothing immediately on the horizon. The mailing list is also not very active, at least today.

I'm going to keep chugging away at it for a few days just to get a firm grasp on it. I always like to know about the latest and greatest frameworks. It helps remind my why I don't like using them. HA. Anyway, more to come as I go along...