A wink at Wicket

Choice is good.
Right now I can happily choose between several frameworks that I'm comfortable and familiar with (Spring, WebWork, Struts) for RAD development in J2EE. Struts seems to have been somewhat stagnant, since about mid-2004, and Spring comes across as having gained a lot of momentum these days.
However, this scenario can change. The "merger" of WebWork and Struts might inject (talk about dependency injection, huh?) new blood (and the good features of WebWork) into Struts; the rate of framework ideas and projects hasn't showed any signs of slowing down (Turbine, Expresso, Tapestry, Cocoon, Maverik, Laszlo, Echo, SOFIA, Verge, VRaptor, Jucas, MyFaces, Chrysalis, Wicket, and, the most recent one in my knowledge, Swato).
Because I want to be aware of developments within the frameworksphere and its future, I've been paying some attention to Wicket recently.
There are some reports claiming very high adoption levels for Wicket, which I frankly find hard to believe. Nevertheless, I'll keep an open mind -and an open eye to its future development.
There is a clean post at Code Poet on creating an Ajax autocomplete field with Wicket which I find attractive in its simplicity:

http://jroller.com/page/wireframe/?anchor=choice_is_good