I'd love to see some built-in interoperability in JSF for GWT. GWT gives you a lot of Ajax firepower (in fact, it's unrivaled, IMO) on the client, and JSF provides lots of firepower on the server. Combining the two technologies is a very attractive proposition.<br>
<br>Grails has a GWT plug-in, and I would love to see JSF have something along those lines.<br><br><br>david<br><br><br><div class="gmail_quote">2009/12/17 Jim Driscoll <span dir="ltr"><<a href="mailto:Jim.Driscoll@sun.com">Jim.Driscoll@sun.com</a>></span><br>
<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">While the wicket fanboys like to bang on pots and pans and make a lot of noise, I think it's important for me to say where I think we should really be paying attention -<br>
<br>
The following 2 Indeed job trends graphs hopefully make my point:<br>
<br>
<a href="http://www.indeed.com/jobtrends?q=jsf%2C+gwt%2C+jquery%2C+yui%2C+dojo%2C+wicket&l=" target="_blank">http://www.indeed.com/jobtrends?q=jsf%2C+gwt%2C+jquery%2C+yui%2C+dojo%2C+wicket&l=</a><br>
<br>
<a href="http://www.indeed.com/jobtrends?q=jsf%2C+php%2C+asp%2C+rails%2C+wicket&l=" target="_blank">http://www.indeed.com/jobtrends?q=jsf%2C+php%2C+asp%2C+rails%2C+wicket&l=</a><br>
<br>
We can learn a thing or two from wicket, but I'd rather learn from or work with technologies that are actually in the process of breaking out, or have already had great success.<br>
<br>
Just something to keep in mind next time you get a derisive tweet.<br><font color="#888888">
<br>
Jim<br>
</font><br>
P.S. And that's also a reminder to me that I really need to look at GWT again. And I still have that action item to examine our interoperability with jQuery more thoroughly.<br>
<br>
P.P.S. Yes, I think jQuery has won the JS framework wars for the time being. The jobs data backs up my anecdotal experience. The breakout appears to have started about 2 years ago.<br>
</blockquote></div><br>