I figure I'm obligated to respond, since my comments were cited in the original email. :)
I have to disagree with complaints about Wicket's complexity, but only because I've been using it to build a product for the last few months. Without heavy usage, I don't think I'd have the same positive opinion. Some things, like displaying conditional content, seemed cumbersome initially, but now I appreciate having the logic in one place, rather than split between the Action and the JSP. Lack of markup in the templates and the concept of a page map have really simplified my development and made features much easier to add, especially when compared to Struts. Not having to update struts-config.xml and validation.xml is also quite nice. I won't use JSF. Tapestry is okay, but still requires some form of configuration either through XML or annotations. Additionally, there's still some logic in the markup. I don't have to do that with Wicket. All that said, I'd prefer if you don't use Wicket. I'd like to keep this competitive advantage to myself. :)
