[ a little re-ordered ] > Can any one please explain me the real advantages of JSF,I > don't Know about > it fully even though I'm using it.
You're using it but don't understand it's advantages? > I feel that the JSF is in > limited Use when COmpared to the other frameworks , the > interest is towards > Spring and hibernate rather than using JSF.. You're trying to compare apples to oranges to grapes here. Each of these tools are solid tools, but they are tools to solve different problems. Hibernate simplifies typical object relational mapping challenges (should be enough said). Spring provides an IOC at it's core, but also an alternative to the overbloated J2EE/JEE stack. JSF provides a simple MVC architecture for constructing web applications. So although each of these tools have some overlaps, they solve different problems. > I would like to know the Positives of the JSF. The positives are numerous, but the ones that sold us are: * Client side support (struts is mostly server side w/little client side support). * No required inheritence (struts and others force an inheritence heirarchy on you). * IOC capabilities (we've grown to love the IOC concept as it keeps individual modules simpler than the non-IOC way). * Testability (you can JUnit test managed beans, but (last I checked) this was not possible or easy under struts). > I would also like to know about the Combinations like JSF > + Spring or JSF+hibernate can work out.. All of the new projects we are working on use JSF, Facelets, Spring, and Hibernate. Our code base, as a result, is greatly simplified; for the most part it looks like a collection of POJOs. IOC across the board ensures that ever object we create is smaller, simpler, and subject to full JUnit testing. I've used many different frameworks and many different development practices, but I have to say that I truly feel this combination is the best I have ever worked with. There's a larger learning curve for the team to get a handle on these 'new' tools, but in the end it is resulting in code/projects that are easier to reuse and maintain. > Is it the fact that people are going back again to Struts and > looking for the Struts 2.0 and get to it. Are they still working on 2.0? I've heard that JSF was to be considered 2.0, I've heard that it was to be abandoned for Shale, and I'm aware that there is a core set of struts-lovers that would prefer incremental updates to struts. All I know is that we have projects underway right now. We needed a modern framework that was built under the modern IOC pattern. JSF fits; struts (in it's current incarnation) does not.
