As said above these frameworks are developed on top of Servlet/JSP.
They are meant to avoid duplication of code (DRY).
Framework are based on Design Patterns - general reusable solution for a commonly occurring problems.
They help communicate the things easily across the team and make them productive and focused on the enterprise level problem they are trying to solve than these common tasks.
They help in speeding up the development by providing general solution to commonly well known problems. (e.g. form validation, REST, testing, dependency injection etc.)
When you are developing large scale enterprise app and have multiple developers working on it, you definitely needs some uniformity across the project/code/structure each developer is writing. The enforcements forced externally are not reliable, but when those are in built it helps to make the project to be easy to maintain, scale and easy for new people to be productive with it within short time.
I believe this rule applies not just for servlet-jsp but for JavaScript as well. Just native JavaScript or even low level JavaScript API/Libraries are not enough when building an enterprise scale UI. Either adopt the Best available Framework or abstract out common nature and make it a framework (not library).
Spring MVC 仍然可以与 JSP 一起使用，其核心只是提供一个简单的调度程序 servlet，该 servlet 使用 Spring MVC 框架提供的机制（您可以在其中注册控制器等）。我想说这是为了方便，让事情更容易编写和维护。此外，您可以更轻松地对当前的开发做出反应（例如，RESTful 服务...您必须在 servlet 中手动编写所有这些内容）。最终这就是框架的用途。
Spring MVC still works with JSPs and in its core it provides nothing more than a simple dispatcher servlet that uses the mechanisms provided by the Spring MVC framework (where you register your controllers in etc.). I would say it is about convenience and making things a lot easier to write and maintain. Additionally you can react more easily to current developments (e.g. RESTful services... you would have to code all of it by hand in a servlet). In the end that is what frameworks are for.
发布评论
评论（2）
我将就此分享一些我的想法。
当您开发大型企业应用程序并有多个开发人员处理它时，您肯定需要每个开发人员编写的项目/代码/结构具有一定的一致性。外部强制执行并不可靠，但当这些执行内置时，它有助于使项目易于维护、扩展，并且易于新人员在短时间内提高工作效率。
我相信这条规则不仅适用于 servlet-jsp，也适用于 JavaScript。在构建企业级 UI 时，仅使用本机 JavaScript 甚至低级 JavaScript API/库是不够的。要么采用最佳可用框架，要么抽象出共性并使其成为一个框架（而不是库）。
I will share some of my thoughts on this.
When you are developing large scale enterprise app and have multiple developers working on it, you definitely needs some uniformity across the project/code/structure each developer is writing. The enforcements forced externally are not reliable, but when those are in built it helps to make the project to be easy to maintain, scale and easy for new people to be productive with it within short time.
I believe this rule applies not just for servlet-jsp but for JavaScript as well. Just native JavaScript or even low level JavaScript API/Libraries are not enough when building an enterprise scale UI. Either adopt the Best available Framework or abstract out common nature and make it a framework (not library).
Spring MVC 仍然可以与 JSP 一起使用，其核心只是提供一个简单的调度程序 servlet，该 servlet 使用 Spring MVC 框架提供的机制（您可以在其中注册控制器等）。我想说这是为了方便，让事情更容易编写和维护。此外，您可以更轻松地对当前的开发做出反应（例如，RESTful 服务...您必须在 servlet 中手动编写所有这些内容）。最终这就是框架的用途。
Spring MVC still works with JSPs and in its core it provides nothing more than a simple dispatcher servlet that uses the mechanisms provided by the Spring MVC framework (where you register your controllers in etc.). I would say it is about convenience and making things a lot easier to write and maintain. Additionally you can react more easily to current developments (e.g. RESTful services... you would have to code all of it by hand in a servlet). In the end that is what frameworks are for.