Originally posted by Mark Spritzler: I'll just point out two
1. JSF is a specification/standard, Struts is not. 2. JSF Spec Lead is the guy who created Struts. And did so trying to fix what he did wrong in Struts.
So will he eventually fix what he did wrong in JSF? ;)
Joined: May 26, 2007
I'll point to another 2: (AFAIK, I don't have too much experience with Struts) 1) JSF lifecycle is not tied to the request-response cycle 2) You can map screen components to individual beans, in Struts you have to map to the Form class.
To be precise, the #1 advantage of JSF over Struts is that it takes something like 5 Struts source files to do what JSF can do in 2, and the JSF source files are simpler - few special functions, no magic classes to extend or interfaces to implement.
It's also more of a "pure" MVC architecture than Struts, although true MVC is architecturally impossible under HTTP. Not that purity is in and of itself a virtue, but it does make it easier to understand what's supposed to be going on.
Customer surveys are for companies who didn't pay proper attention to begin with.