15 lines
798 B
Plaintext
15 lines
798 B
Plaintext
|
[[mvc-view]]
|
||
|
|
= View Technologies
|
||
|
[.small]#<<web-reactive.adoc#webflux-view, 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 <<mvc-viewresolver>>.
|
||
|
|
||
|
|
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.
|
||
|
|
|