![]() Through it at all when using JSF with Spring Web Flow. Normally would even though you generally will not need to route requests In order for JSF to bootstrap correctly, theįacesServlet must be configured in web.xml as it Spring MVC Dispatcher Servlet .DispatcherServlet contextConfigLocation /WEB-INF/web-application-config.xml 1 Spring MVC Dispatcher Servlet /spring/* Is the location of the Spring configuration for your webĪpplication. Used in the servlet to pass the contextConfigLocation. In thisĮxample, we map all URLs that begin with /spring/ to the xml is not a problem as long you have a good process to manage it -).The first step is to route requests to theĭispatcherServlet in the web.xml file. Spring is not "xml" and "verbose" since it delivers the full set of annotations support (Spring release 2.5). If your backend is Spring based the presentation integrates pretty seamlessly. I suggest to use Spring DI managed beans instead of the standard JSF managed beans in any case. ![]() So, for the enterprise developer with a lot of requirements to implement in a modern Web application ICEfaces is maybe the better solution. ICEfaces allows to implement pretty complex presentations without getting into scalability problems. ![]() Also do this for the other frameworks you think about. So, try to implement a prototype to get a feeling for the pros and cons. All this depends on the presentation you want to generate in the browser, of course. This can be pretty complicate and you can get into maintenance and scalability problems. But, what I understand is that you generate a lot of application code in the client side. 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 :-) 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. 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. 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. and finaly droping most of the Struts 1.x part. As we know Struts 1.x changged completly to become Struts 2.x, it was done merging Struts 1.z and WebWork. Struts: Struts 1.x is almost dead, so we need to write about Struts 2.x (WebWork). 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). ![]() 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. ![]() 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. 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. 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). ![]()
0 Comments
Leave a Reply. |