Pros and Cons of MVC frameworks

Struts
Pros:
* The “Standard” - lots of Struts jobs
* Lots of information and examples
* HTML tag library is one of the best
Cons:
* ActionForms - they’re a pain
* Can’t unit test - StrutsTestCase only does integration
* Project has been rumored as “dead”


Spring MVC
Pros:
* Lifecyle for overriding binding, validation, etc.
* Integrates with many view options seamlessly: JSP/ JSTL, Tiles, Velocity, FreeMarker,
Excel, XSL, PDF
* Inversion of Control makes it easy to test
Cons:
* Configuration intensive - lots of XML
* Requires writing lots of code in JSPs
* Almost too flexible - no common parent Controller

WebWork
Pros:
* Simple architecture - easy to extend
* Tag Library is easy to customize with FreeMarker or Velocity
* Interceptors are pretty slick
* Controller-based or page-based navigation
Cons:
* Small Community
* Documentation is poorly organized


Tapestry
Pros:
* Very productive once you learn it
* Templates are HTML - great for designers
* Healthy and smart user community
Cons:
* Documentation very conceptual, rather than pragmatic
* Steep learning curve - very few examples
* Long release cycles - major upgrades every year


JSF
Pros:
* J2EE Standard - lots of demand and jobs
* Fast and easy to develop with
* Rich Navigation framework
Cons:
* Tag soup for JSPs
* Doesn't play well with REST or Security
* No single source for implementation