File APIs for Java Developers
Manipulate DOC, XLS, PPT, PDF and many others from your application.
http://aspose.com/file-tools
The moose likes JSF and the fly likes ICEFaces,  how is it different or similar to Spring/GWT/Struts Big Moose Saloon
  Search | Java FAQ | Recent Topics | Flagged Topics | Hot Topics | Zero Replies
Register / Login
JavaRanch » Java Forums » Java » JSF
Bookmark "ICEFaces,  how is it different or similar to Spring/GWT/Struts" Watch "ICEFaces,  how is it different or similar to Spring/GWT/Struts" New topic
Author

ICEFaces, how is it different or similar to Spring/GWT/Struts

Nikes Shah
Ranch Hand

Joined: Jul 18, 2007
Posts: 133
How ICEFaces different or similar to other frameworks like GWT/Spring/Struts?

Advantages over other competitive frameworks?

Rahul Juneja
Ranch Hand

Joined: Aug 03, 2002
Posts: 425
Icefaces is little better then these frameworks incase you want a good ajax based user interface with little or no javascript at all. as it provides a rich set of jsf library which is easy to use and plug it in your application.

Thanks,
Rahul


Rahul Juneja
ThoughtClicks - http://techlabs.thoughtclicks.com
Nikes Shah
Ranch Hand

Joined: Jul 18, 2007
Posts: 133
Thanks for reply Rahul.

Icefaces is little better then these frameworks incase you want a good ajax based user interface with little or no javascript at all. as it provides a rich set of jsf library which is easy to use and plug it in your application.


Better in what sense? Speed of development? Security? Good looking User Interface?


as it provides a rich set of jsf library which is easy to use and plug it in your application.


We can also avoid typing javascript by using GWT which converts Java code to Javascript. So how is it different?

Our team have to decide on which framework to use for one of our upcoming web project,
so just wanted to get more inside top level comparision.
Hayrol Reyes Mejía
Greenhorn

Joined: Dec 01, 2009
Posts: 4
I a few words (well, not so few):

GWT: is a "too Googly" ajax framework (imho), very nice but I don't like the idea of turn almost all the Java code into html and JS AJAX (it's not an easy comparation, 'cus diferent concepts). Also, to compare with ICEFaces you need to see into GWT MVC, which is a attemp to expand the framework, building a MVC capable framework above the GWT thenology.

Spring: too xml verbose. DI (and IO) are the heart of Spring, but you can't compare with ICEFaces 'cus Spring have several parts and Spring Web Flow development is not the best part, even implementing a MVC patter. Btw, ICEFaces development has a smoothly integration with Springframework DI (not Spring Web Flow), and if you like it and you can deal with too much xml's configuration, then you can build very good applications. In other words you can use ICEFaces to replace Spring Web Flow and part of Spingframework to develop the core application's services (DI and more).

Struts: Struts 1.x is almost dead, so we need to write about Struts 2.x (WebWork). As we know Struts 1.x changged completly to become Struts 2.x, it was done merging Struts 1.z and WebWork ... and finaly droping most of the Struts 1.x part. Struts, was a "the facto" MVC Web development framework, but it has several problems mainly due to its Page Control Centric approach, when JSF become to the scena, with component and event control (well, the man that make Struts 1, worked on JSF 1 too), then JSF turn into "the facto" MVC web development framework, even more becouse JSF was a standard and was designed to be extensible.

ICEFaces: It's a JSF implementation with build-in AJAX extension (and others) integrated completly into the framework, therefore, ICEFaces is a MVC web development framework extended with AJAX. The best part is that it's a powerfull framework and you don't need to write a single line of JavaScripts, just concentrate on Java Development (to build the View and the Control of the MVC patter), and use the compenent in the framework or build yours. Of course, you need to integrate some sort of technology to build your model, we say: EJB3+JPA, Springframework+JDBC, Springframework+JPA,Java Classes+JDO, Java Clasess+JDBC, and so on :-)
Rainer Eschen
author
Ranch Hand

Joined: Jan 24, 2009
Posts: 75
I never had a look at GWT. But, what I understand is that you generate a lot of application code in the client side. This can be pretty complicate and you can get into maintenance and scalability problems. All this depends on the presentation you want to generate in the browser, of course. So, try to implement a prototype to get a feeling for the pros and cons. Also do this for the other frameworks you think about.

ICEfaces allows to implement pretty complex presentations without getting into scalability problems. So, for the enterprise developer with a lot of requirements to implement in a modern Web application ICEfaces is maybe the better solution.

I suggest to use Spring DI managed beans instead of the standard JSF managed beans in any case. If your backend is Spring based the presentation integrates pretty seamlessly. Our experiences are pretty good with it.
Spring is not "xml" and "verbose" since it delivers the full set of annotations support (Spring release 2.5). xml is not a problem as long you have a good process to manage it ;-).


ICEfaces book . ICEcube . ICEfusion . Scrum
Nikes Shah
Ranch Hand

Joined: Jul 18, 2007
Posts: 133
Thanks All.

I would give a try for ICEFaces
 
 
subject: ICEFaces, how is it different or similar to Spring/GWT/Struts