Struts and Turbine I have used it and have done a project, I want to say something in this question :-)
Struts is much simpler than Turbine. In other words, Struts is a very pure web framework, which is just just a Framework.Struts that says it complies with MVC, I don't agree. Struts is very good It has completed VC (Visual & Control), but it does not provide corresponding M (Module), or not obvious. Struts is the best partner may be EJB, because EJB adds its M.
Turbine, it is not a full solution for a web application. Turbine is not very compliant with J2EE standard. It has its own solution, it is a true MVC mode frame. It has A large number of sub-projects support its application (subproject tree is second only to Jarkarta Commons)
Turbine is difficult to understand, difficult to learn, but master it is meaningful. If you just want to write a web app, Turbine is fast than Struts.
Turbine supports Velocity, WebMacro, Cocoon (XSLT), etc., although it also supports JSP, but its most close arms are Velocity.
Struts may be very straightforward to write JSP and servlet. The related items of Jakarta project group provide a large number of TAGs to support struts, making Struts's structural and uniformity, another one of Struts Turbine is not as good as its mapping-forward mechanism, in Struts, is managed with struts-config.xml files, although this XML file becomes great so as to maintain as your project is expanded. There will be a special person to manage this file in a big project), but its unity and navigation logic are much better than Turbine. Turbine controls the corresponding logic to control. In the corresponding Velocity page, navigation.
