This week's book giveaway is in the OO, Patterns, UML and Refactoring forum. We're giving away four copies of Refactoring for Software Design Smells: Managing Technical Debt and have Girish Suryanarayana, Ganesh Samarthyam & Tushar Sharma on-line! See this thread for details.
Because a GWT is based on AJAX, it is likely to perform slightly better than either Struts or JSF, mainly because it makes individual updates to the page, rather than refreshing the entire page.
However, because much more code runs on the browser in a GWT application, how well it performs will depend on the speed of the client system (i.e. the PC running the browser).
Regarding startup time, I would argue that it's not something you should worry about. In most production systems, the server starts up once and is rarely ever stopped except to do maintenance. What does it matter if it takes the web application a while to load up on the server? It's only going to happen once.
Does GWT provide what struts do? if i have struts application and i want to migrate it to GWT,will i miss any thing or will i lost some thing?
Joined: Feb 15, 2005
GWT and Struts are both frameworks for developing web-based applications, but there the similarities end. They use a completely different paradigm. Struts just builds on the standard Java EE request/response pattern, while with GWT, every call to the server is an AJAX call, and manipulation of the web page is done through standardized "widgets" that are defined in the toolkit.
I guess you don't really lose anything if you switch from Struts to the GWT, but you will have to get used to a completely different way of thinking about developing web applications.
Joined: Nov 02, 2004
But i have one question,what about support? Will i found materials that cover GWT and if i need support will i found it or it will be diffecult as GWT is considered new technology?
Joined: Feb 15, 2005
My personal opinion is that you will find better support for either JSF or Struts than you will for GWT.
One other comment as well: I don't believe it's a good practice to choose a framework solely on the basis of expected runtime performance. There are a lot of factors that affect runtime performance, and the framework is only one of them.
I heartily concur with comments made on this subject by Joe Ess in this thread.