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

[[mvc-view]]
= View Technologies
:page-section-summary-toc: 1
[.small]#xref:web/webflux-view.adoc[See equivalent in the Reactive stack]#

The use of view technologies in Spring MVC is pluggable. Whether you decide to use
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.
We assume you are already familiar with xref:web/webmvc/mvc-servlet/viewresolver.adoc[View Resolution].

WARNING: The views of a Spring MVC application live within the internal trust boundaries
of that application. Views have access to all the beans of your application context. As
such, it is not recommended to use Spring MVC's template support in applications where
the templates are editable by external sources, since this can have security implications.
Provide distinct Web and Reactive Web sections This change allows much more usable TOC for the reactive stack and will make WebFlux documentation easier to contribute thanks to a clearer split between both stacks. Issue: SPR-15149 2017-08-23 22:00:26 +08:00			`[[mvc-view]]`
			`= View Technologies`
Enable Section Summary TOC for small pages 2023-04-19 23:26:17 +08:00			`:page-section-summary-toc: 1`
Fix cross references 2023-04-19 23:26:17 +08:00			`[.small]#xref:web/webflux-view.adoc[See equivalent in the Reactive stack]#`
Consistent separation between chapters and after chapter titles 2017-10-19 02:24:17 +08:00
Polishing 2020-06-17 19:35:14 +08:00			`The use of view technologies in Spring MVC is pluggable. Whether you decide to use`
			`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.`
Fix cross references 2023-04-19 23:26:17 +08:00			`We assume you are already familiar with xref:web/webmvc/mvc-servlet/viewresolver.adoc[View Resolution].`
Modularize asciidoc documentation The reference documentation is now organized in asciidoc bookparts. Bookparts sections can be also put in separate files, when their size and theme are important enough to justify that. Documentation Layout: ``` index \|-- overview \| \|-- whats-new \| \|-- core \| \|-- core-beans \| \|-- core-aop \|-- testing \| \|-- data-access \| \|-- web \| \|-- web-mvc \| \|-- web-view \|-- integration \| \|-- appendix \|-- appx-spring-tld \|-- appx-spring-form-tld ``` Supersedes and closes #641 Issue: SPR-12309 2015-03-03 18:38:01 +08:00
Polishing 2020-06-17 19:35:14 +08:00			`WARNING: The views of a Spring MVC application live within the internal trust boundaries`
			`of that application. Views have access to all the beans of your application context. As`
			`such, it is not recommended to use Spring MVC's template support in applications where`
			`the templates are editable by external sources, since this can have security implications.`
Asciidoc revision (chapter declarations, javadoc references, etc) 2018-10-25 21:15:58 +08:00