a BindException instead of derive from it * interfaces HandlerAdapter, HandlerMapping, and ViewResolver do not require ApplicationContextAware anymore * interface View does not require addStaticAttribute

使用@RequestMapping注解映射请求路径 定义@RequestMapping注解的处理方法 异步请求的处理 对控制器测试 处理器映射 使用HandlerInterceptor拦截请求 视图解析 使用ViewResolver接口解析视图 视图链 视图重定向 内容协商解析器ContentNegotiatingViewResolver使用闪存属性FlashAttributes URI构造 为控制器和方法指定URI 模型、填充数据、返回一个合适的视图名等，同时它也可以直接将数据写到响应流中。视图名的解析高度灵活，支持多种配置，包括通过文件扩展名、Accept 内容头、bean、配置文件等的配置，甚至你还可以自己实现一个视图解析器 ViewResolver 。模型（MVC中的M，model）其实是一个 Map 类型的接口，彻底地把数据从视图技术中抽象分离了出来。你可以与基于模板的渲染技术直接整合，如JSP、Velocity和 Freemar rServlet屏蔽这些具体的细节。 HandlerExceptionResolver 处理器异常解析器。它负责将捕获的异常映射到不同的视图上去，此外还支持更复杂的异常处理代码。 ViewResolver 视图解析器。它负责将一个代表逻辑视图名的字符串（String）映射到实际的视图类型View上。 LocaleResolver & LocaleContextResolver 地区解析

mapping them to handlers, to HTML error views, or other targets. See Exceptions.ViewResolverResolve logical String-based view names returned from a handler to an actual View with WebFlux Spring MVC defines the ViewResolver and View interfaces that let you render models in a browser without tying you to a specific view technology. ViewResolver provides a mapping between view names table provides more details on the ViewResolver hierarchy: ### Table 3. ViewResolver implementations |ViewResolver|Description| |---|---| |AbstractCa

resolution is highly configurable, either via bean names, via a properties file, or via your own ViewResolver implementation. The abstract model Map allows for complete abstraction of the view technology handles views are the ViewResolver and the View. The View interface addresses the preparation of the request and hands the request over to one of the view technologies. The ViewResolver provides a mapping resolved by a viewresolver. Spring comes with quite a few view resolvers. We'll list most of them and then provide a couple of examples. Table 12.5. View resolvers |ViewResolver|Description| |---|---|

resolution is highly configurable, either via bean names, via a properties file, or via your own ViewResolver implementation. The abstract model Map allows for complete abstraction of the view technology handles views are the ViewResolver and the View. The View interface addresses the preparation of the request and hands the request over to one of the view technologies. The ViewResolver provides a mapping resolved by a viewresolver. Spring comes with quite a few view resolvers. We'll list most of them and then provide a couple of examples. Table 12.5. View resolvers |ViewResolver|Description| |---|---|

resolution is highly configurable, either via bean names, via a properties file, or via your own ViewResolver implementation. The abstract model Map allows for complete abstraction of the view technology handles views are the ViewResolver and the View. The View interface addresses the preparation of the request and hands the request over to one of the view technologies. The ViewResolver provides a mapping resolved by a viewresolver. Spring comes with quite a few view resolvers. We'll list most of them and then provide a couple of examples. Table 12.5. View resolvers |ViewResolver|Description| |---|---|

resolution is highly configurable, either via bean names, via a properties file, or via your own ViewResolver implementation. The abstract model Map allows for complete abstraction of the view technology handles views are the ViewResolver and the View. The View interface addresses the preparation of the request and hands the request over to one of the view technologies. The ViewResolver provides a mapping resolved by a viewresolver. Spring comes with quite a few view resolvers. We'll list most of them and then provide a couple of examples. Table 12.5. View resolvers |ViewResolver|Description| |---|---|

resolution is highly configurable, either via bean names, via a properties file, or via your own ViewResolver implementation. The abstract model Map allows for complete abstraction of the view technology technologies. The two interfaces which are important to the way Spring handles views are ViewResolver and View. The ViewResolver provides a mapping between view names and actual views. The View interface addresses We'll list most of them and then provide a couple of examples. Table 12.5. View resolvers |ViewResolver|Description| |---|---| |AbstractCachingViewResolver|An abstract view resolver which takes care

resolution is highly configurable, either via bean names, via a properties file, or via your own ViewResolver implementation. The abstract model Map allows for complete abstraction of the view technology technologies. The two interfaces which are important to the way Spring handles views are ViewResolver and View. The ViewResolver provides a mapping between view names and actual views. The View interface addresses We'll list most of them and then provide a couple of examples. Table 12.5. View resolvers |ViewResolver|Description| |---|---| |AbstractCachingViewResolver|An abstract view resolver which takes care