I'm debating whether to use Seam, Wicket, JSF or GWT as the foundation for my presentation layer in a Java project.
I narrowed my selection of Java web frameworks down to this subset based on job market considerations, newness of the technology and recommendations from other S.O. users.
What factors should I take into consideration in deciding among these?
I've used Wicket and GWT pretty heavily. Never really learned to love Wicket.
My ego blogged about it http://salk31.blogspot.com/2009/07/wicket-ajax.html
Looking at GWT 2.0 uiBinder today reminded me how annoying it was in Wicket to have to match the XML component tree with the one created in Java. The GWT spin on this looks vastly better to me.
I've not used Wicket for over a year so maybe they have fixed a lot of this but given modern browser and JS support I can't see the point of doing all this on the server (I know, I know data locality).
JSF is deprecated (JSF is not even listed as a framework to compare when evangelists compare or talk about web frameworks in 2010).
Now full fledge large scale applications are created using GWT, YUI, JQuery etc.
Read some articles over google and above will be obvious.
(ALL JOBS on JSF are to support legacy applications).