Browse Source

Modernize View Technologies section (#35450)

Signed-off-by: albonidrizi <albonidrizi@gmail.com>
pull/36010/head
albonidrizi 7 days ago
parent
commit
d29e143216
  1. 5
      framework-docs/modules/ROOT/pages/web/webmvc-view.adoc

5
framework-docs/modules/ROOT/pages/web/webmvc-view.adoc

@ -8,6 +8,11 @@ The rendering of views in Spring MVC is pluggable. Whether you decide to use
Thymeleaf, Groovy Markup Templates, JSPs, or other technologies is primarily a matter of Thymeleaf, Groovy Markup Templates, JSPs, or other technologies is primarily a matter of
a configuration change. This chapter covers view technologies integrated with Spring MVC. a configuration change. This chapter covers view technologies integrated with Spring MVC.
[TIP]
====
Spring MVC prioritizes Java-based configuration. While XML configuration is supported for legacy applications, we recommend using `@Configuration` classes and equivalent Java-based APIs for all new projects.
====
For more context on view rendering, please see xref:web/webmvc/mvc-servlet/viewresolver.adoc[View Resolution]. For more context on view rendering, please see xref:web/webmvc/mvc-servlet/viewresolver.adoc[View Resolution].
WARNING: The views of a Spring MVC application live within the internal trust boundaries WARNING: The views of a Spring MVC application live within the internal trust boundaries

Loading…
Cancel
Save