The spring web MVC Framework provides many unique functions, including:
Clear roles: controller, validator, command object, form object, and model object), Servlet distributor (DispatcherServlet), Processor mapping, view resolver, and so on. Each role can be implemented by a special object.
Powerful and direct configuration method: the framework class and application class are both configured as JavaBean. JavaBean of other context can be referenced in one context. For example, references Business Objects and validators in Web controllers.
Adaptive and non-intrusive Controller: You can use different application scenarios, select the appropriate controller subclass (simple, command, form, wizard, multi-action, or custom), instead of inheriting from a single controller (such as Action/actionform.
Reusable business code: You can use existing business objects as command or form objects without repeating their definitions in subclass similar to actionform.
Customizable binding and validation: for example, if the Type mismatch is used as an application-level verification error, the error value can be saved. For example, the localized date and number binding. In some other frameworks, you can only use string form objects. You need to manually Parse them and convert them to business objects.
Customizable handler mapping and view resolution: Spring provides simple URL ing to complicated and dedicated custom policies. Compared with some MVC frameworks that force developers to use a single specific technology, spring is more flexible. Flexible.
Flexible model conversion: In the springweb frameworkMapTo easily integrate with various view technologies.
Customizable localization and theme parsing: Spring label library can be selected in JSP, jstl, velocity (no additional Middle Layer required), and so on.