Tim O’Brien, after his previous criticism of Struts 2, did some homework on Wicket, a framework he mentioned in the prior piece. I have not used Wicket, but this seems pretty objective and informed. I would still do a bake off between it and what I am used to, Struts 1, and other likely candidates, before given my own opinions. But this at least gives a good survey of what to expect when playing with Wicket. Sounds like wait and see may be helpful in the sense that it would at least give the documentation and APIs a chance to for some much needed simmering.