I have used it and have been used in this issue. I want to say something in this question :-) Struts is simpler than Turbine's structure, in turn, Struts is a very pure web framework, It is just just a Framework.Struts that says it complies with MVC. I am not very recognized. Struts has completed VC (Visual & Control), but it does not provide corresponding M (Module), or Say that the best partner of Struts may be EJB, because EJB adds its M. and turbine, its design ideas determine it is a full solution for a web application. Turbine is not very compliant with J2EE standard It has its own set of solutions, it is a true MVC mode framework. It has a large number of sub-projects to support its application (sub-project tree is second only to Jarkarta Commons) Turbine is difficult than Struts Understand, hard to learn, but master it is meaningful. If you just want to write a web app, Turbine is developing more .Turbine supports Velocity, WebMacro, Cocoon (XSLT), etc., although it also supports JSP, but Its most intimate war friend is Velocity.Struts may be very straightforward for people who write JSP and servlet. The related items of Jakarta project group provide a lot of TAG to support struts to make Struts structure and Uniformity becomes very good, another Turbine of Struts is not as good as its mapping-forward mechanism, which is managed in Struts, although this XML file is used as your project is expanded. It will become very difficult to maintain (generally a special project will manage this file), but its unity and navigation logic are much better than Turbine, Turbine controls the corresponding logic to control. The relevant navigation is also used in the corresponding Velocity page.
