_1.jpg) ## 大纲 转换器和格式化（Converter and Formatter） 验证器 表达式语言（EL） JSTL ## 接下来… 转换器和格式化（Converter and Formatter） 验证器 表达式语言（EL） JSTL ## 转换器和格式化（Converter and Formatter） Spring MVC 框架具备数据自动绑定能力，但其数据 Formatter，自行搜索学习。 ## 接下来… 转换器和格式化（Converter and Formatter） 验证器 表达式语言（EL） JSTL ## 验证器 输入验证是 Spring 处理的最重要 Web 开发任务之一。在 Spring MVC 中，可以利用 Spring 自带的验证框验证用户输入。 ▶ Converter 和 Formatter ice"); ## Spring MVC Validation 示例 ## 接下来… 转换器和格式化（Converter and Formatter） 验证器 表达式语言（EL） JSTL ## 表达式语言 JSP2.0 最重要的特性之一就是表达式语言（EL），可以用它来访问应用程序数据。 EL 设计成可以轻松地编写免脚本的 JSP 页面，而不需要使用任何 JSP 声明、表达式等元素。

ApplicationContext to be set anymore (allowing for "getServletContext" checking) * JstlView, Tiles(Jstl)View and AbstractJasperReportsView expose current RequestContext's MessageSource for localization Loop" to "true" for conventional name-based View instances only * JstlView exposes a JSTL-aware MessageSource even for a custom MessageSource passed in through the constructor * re-added JstlView detects session-scoped JSTL LocalizationContext/Locale attributes and merges them with its own context * JstlView and (JspAware)RequestContext consistently use JSTL Config class for scoped attribute

ApplicationContext to be set anymore (allowing for "getServletContext" checking) * JstlView, Tiles(Jstl)View and AbstractJasperReportsView expose current RequestContext's MessageSource for localization Loop" to "true" for conventional name-based View instances only * JstlView exposes a JSTL-aware MessageSource even for a custom MessageSource passed in through the constructor * re-added JstlView detects session-scoped JSTL LocalizationContext/Locale attributes and merges them with its own context * JstlView and (JspAware)RequestContext consistently use JSTL Config class for scoped attribute

137 13.1. Introduction ..... 137 13.2. JSP & JSTL ..... 137 13.2.1. View resolves ..... 137 13.2.2. 'Plain-old' JSPs versus JSTL ..... 137 13.2.3. Additional tags facilitating development Customizable locale and theme resolution, support for JSPs with and without Spring tag library, support for JSTL, support for Velocity without the need for extra bridges, etc. - Simple but powerful tag library coupled to the MVC framework. #### 13.2. JSP & JSTL Spring provides a couple of out-of-the-box solutions for JSP and JSTL views. Using JSP or JSTL is done using a normal viewresolver defined in the

136 13.1. Introduction ..... 136 13.2. JSP & JSTL ..... 136 13.2.1. View resolves ..... 136 13.2.2. 'Plain-old' JSPs versus JSTL ..... 136 13.2.3. Additional tags facilitating development Customizable locale and theme resolution, support for JSPs with and without Spring tag library, support for JSTL, support for Velocity without the need for extra bridges, etc. - Simple but powerful tag library coupled to the MVC framework. #### 13.2. JSP & JSTL Spring provides a couple of out-of-the-box solutions for JSP and JSTL views. Using JSP or JSTL is done using a normal viewresolver defined in the

ApplicationContext to be set anymore (allowing for "getServletContext" checking) * JstlView, Tiles(Jstl)View and AbstractJasperReportsView expose current RequestContext's MessageSource for localization InternalResourceViewResolver sets "preventDispatchLoop" to "true" for * JstlView exposes a JSTL-aware MessageSource even for a custom MessageSource passed in through the constructor * re-added JstlView detects session-scoped JSTL LocalizationContext/Locale attributes and merges them with its own context * JstlView and (JspAware)RequestContext consistently use JSTL Config class for scoped attribute

131 13.1. Introduction ..... 131 13.2. JSP & JSTL ..... 131 13.2.1. View resolvers ..... 131 13.2.2. 'Plain-old' JSPs versus JSTL ..... 131 13.2.3. Additional tags facilitating development Customizable locale and theme resolution, support for JSPs with and without Spring tag library, support for JSTL, support for Velocity without the need for extra bridges, etc. - Simple but powerful tag library coupled to the MVC framework. #### 13.2. JSP & JSTL Spring provides a couple of out-of-the-box solutions for JSP and JSTL views. Using JSP or JSTL is done using a normal viewresolver defined in the

getVariableResolver, overloaded include) * added MockExpressionEvaluator for JSP 2.0, delegating to the Jakarta JSTL ExpressionEvaluatorManager * deprecated MockHttpServletRequest's "addRole" method expressions in Spring's JSP tags will be parsed with JSP 2.0 ExpressionEvaluator on JSP 2.0 (Jakarta JSTL else) * changed "spring:transform" tag's "value" attribute from String to Object RequestContext works outside DispatcherServlet too, falling back to root WebApplicationContext and JSTL/request locale * added JspAwareRequestContext as subclass of RequestContext, populated from JSP

p" to "true" for conventional name-based View instances only * JstlView exposes a JSTL-aware MessageSource even for a custom MessageSource passed in through the constructor * re-added JstlView detects session-scoped JSTL LocalizationContext/Locale attributes and merges them with its own context * JstlView and (JspAware)RequestContext consistently use JSTL Config class for scoped attribute * InternalResourceViewResolver uses JstlView as default (instead of InternalResourceView) if the JSTL API is present * JSP MessageTag resolves arguments in default text even if no message code was specified

137 13.1. Introduction ..... 137 13.2. JSP & JSTL ..... 137 13.2.1. View resolvers ..... 137 13.2.2. 'Plain-old' JSPs versus JSTL ..... 137 13.2.3. Additional tags facilitating development Customizable locale and theme resolution, support for JSPs with and without Spring tag library, support for JSTL, support for Velocity without the need for extra bridges, etc. - Simple but powerful tag library coupled to the MVC framework. #### 13.2. JSP & JSTL Spring provides a couple of out-of-the-box solutions for JSP and JSTL views. Using JSP or JSTL is done using a normal viewresolver defined in the