This post originated from an RSS feed registered with Java Buzz
by Jason Carreira.
Original Post: The Current State of JSF: continued...
Feed Title: Jason Carreira
Feed URL: http://sedoparking.com/search/registrar.php?domain=®istrar=sedopark
Feed Description: Personal Aggrandizement
Matt Raible stirred up a hornet‘s nest with his take on JSF and it‘s gone back and forth on TSS. Craig McC even showed up, to say this (excerpted):
I believe one of the keys to early adoption of JSF is that tools doexist to support it.
...
After JSP came out, it took about three yearsfor there to be reasonably useful tools to support it. Indeed, one could argue that even tools today haven't done all they could (in part because writing tools for pure JSP is still pretty difficult). In the three monthsafter JSF went final, we saw announcements, and early deliveries, of tools of all sizes that support JSF, and a clear market direction that this will increase. To me, that's a good early indicator that JSF even the current initial version is going to get adopted early and often.
There‘s a lot of tool support for Entity Beans as well, and that‘s all I have to say on that.
I‘d like to point out that there are a lot of GUI builders for Swing, yet the best Swing IDEs are built by hand. Swing was also a de-facto standard, but along came SWT and took a lot of mindshare.
Standard != Success
Tools != Success
in the end, tools only help so much, and once you get past an application of a certain size, GUI tools aren‘t going to cut it and you‘re going to have to do it by hand. Better to be using a framework that‘s friendly to do by hand than one that‘s not. Note: I‘m not including Struts as one that‘s easy to do by hand. I think the fact that so many people use XDoclet for their Struts stuff says a lot… I‘ve come to see Xdoclet as a symptom of a bigger problem with a framework.
Previous Topic
