ongwt.com

Niraj :

GWT in 2008 is going to be the real winner. About an year ago I had posted that 2007 would be the year for GWT . Well looking at the numbers I think it was. It has not overtaken struts but the relative growth has been the highest - 30,000 % WOW!.

Struts , JSF , spring mvc , GWT - what is it going to be

no comment

Here is a demonstration of GWT/JSF integration.
http://livedemo.exadel.com/a4j-gwtdemo/

no comment

Rob :

"...using JSF and GWT together is more complex than just using one or the other. So consider whether you really need both..."

Can i use GWT to make JSF components AJAX enabled?

no comment

It is not easy to integrate server side frameworks (Spring, Acegi, Struts, JSF,...) with GWT. Here is a good patch.
It helps to implement custom server side handlers for GWT-RPC requests.
Refactor RPC out of RemoteServiceServlet

no comment

Michael Jouravlev :

What are benefits of ICEFaces comparing to Google Web Toolkit? This is what I could come up with. Granted, I haven't used ICEFaces yet, so something may be wrong in this list.

Similar features
GWT: J2EE-based, ICEFaces: same.
GWT: Ajax only, ICEFaces: can be rendered with Javascript turned off, but will not submit.
GWT: has basic set of widgets, ICEFaces: same.
GWT: can be easily styled with CSS, ICEFaces: same (?)
GWT: does not need knowledge of Javascript, ICEFaces: same (?)
GWT: UI elements can be properly resized by browser controls, ICEFaces: same
GWT: UI elements can be combined with static HTML, ICEFaces: same

GWT benefits
GWT: views are developed fully with Java, ICEFaces: requires JSF tags
GWT: can be easily debugged, ICEFaces: not so
GWT: clean separation of concerns between UI and server, ICEFaces: ?
GWT: talks to standard servlet, ICEFaces: requires JSF
GWT: widgets are easily extensible, ICEFaces: ?

ICEFaces benefits
???

Old but interesting thread.

ICEFaces vs GWT

2 comments

Ajax On Java :

This practical guide shows you how to make your Java web applications more responsive and dynamic by incorporating new Ajaxian features, including suggestion lists, drag-and-drop, and more. Java developers can choose between many different ways of incorporating Ajax, from building JavaScript into your applications "by hand" to using the new Google Web Toolkit (GWT).
The book branches out into different approaches for incorporating Ajax, which include:

• The Prototype and script.aculo.us Javascript libraries, the Dojo and Rico libraries, and DWR

• Integrating Ajax into Java ServerPages (JSP) applications

• Using Ajax with Struts

• Integrating Ajax into Java ServerFaces (JSF) applications

• Using Google's GWT, which offers a pure Java approach to developing web applications: your client-side components are written in Java, and compiled into HTML and JavaScript

no comment

Wesley Hales

For the last few weeks I have been trying to integrate back button support into my companies JSF/Ajax app as an "Undo" feature. I have been using 2 approaches, 1) g4jsf (a subproject of Ajax4JSF) to enable use of GWT, and 2) dojo.undo.browser.

JSF, Ajax and the Back Button

no comment

JSF Resources :

The very cool Ajax4jsf project now has some excellent integration with the Google Web Toolkit, and Sergery Smirnov has written a tutorial showing how to use the two libraries together. He also states: “The mission of the G4jsf subproject is to shift the perception of the relationship between GWT and JSF from viewing them as competitive technologies to viewing them as naturally complementary technologies.”

G4JSF

no comment

Jay Chauhan : "I recently took a deep look into GWT and I say this is phenomenal. Also, I did exploration of JSF. This group has a lot of discussion about fusing JSF and GWT and at first this sounds a good idea, however, the question yet to be answered is why would you like to fuse GWT with JSF?? "
Interesting.

I'm worried for the future of JSF

no comment