跟我学SpringMVC目录汇总贴、PDF下载、源码下载
电子书下载链接 请登录后下载
在线版目录
第一章 Web MVC简介
第二章 Spring MVC入门
第三章 DispatcherServlet详解
第四章 Controller接口控制器详解（1）
第四章 Controller接口控制器详解（2）
第四章 Controller接口控制器详解（3）
第四章 Controller接口控制器详解（4）
第四章 Controller接口控制器详解（5）
第四章 Controller接口控制器详解（6）
第五章 处理器拦截器详解
第六章 注解式控制器详解 注解式控制器运行流程及处理器定义
第六章 注解式控制器详解 SpringMVC3强大的请求映射规则详解
第六章 注解式控制器详解 Spring MVC 3.1新特性 生产者、消费者请求限定
第六章 注解式控制器详解 SpringMVC强大的数据绑定（1）
第六章 注解式控制器详解 SpringMVC强大的数据绑定（2）
第七章 注解式控制器的数据验证、类型转换及格式化 SpringMVC数据类型转换
第七章 注解式控制器的数据验证、类型转换及格式化 SpringMVC数据格式化
第七章 注解式控制器的数据验证、类型转换及格式化 SpringMVC数据验证
源代码下载——第七章 注解式控制器的数据验证、类型转换及格式化
源代码下载 第六章 注解式控制器详解
源代码下载 第五章 处理器拦截器详解——跟着开涛学SpringMVC
第四章 Controller接口控制器详解 源代码下载
第二章 Spring MVC入门 源代码下载
跟着开涛学SpringMVC 第一章源代码下载
《跟我学Spring3》目录贴点击前往
一、《跟我学spring3》电子书下载地址：
《跟我学spring3》 （1-7 和 8-13）http://jinnianshilongnian.iteye.com/blog/pdf
二、源代码下载
【第一章】 Spring概述 ——跟我学Spring3
【第二章】 IoC 之 2.1 IoC基础 ——跟我学Spring3
【第二章】 IoC 之 2.2 IoC 容器基本原理 ——跟我学Spring3
【第二章】 IoC 之 2.3 IoC的配置使用——跟我学Spring3
【第三章】 DI 之 3.1 DI的配置使用 ——跟我学spring3
【第三章】 DI 之 3.2 循环依赖 ——跟我学spring3
【第三章】 DI 之 3.3 更多DI的知识 ——跟我学spring3
【第三章】 DI 之 3.4 Bean的作用域 ——跟我学spring3
【第四章】 资源 之 4.1 基础知识 ——跟我学spring3
【第四章】 资源 之 4.2 内置Resource实现 ——跟我学spring3
【第四章】 资源 之 4.3 访问Resource ——跟我学spring3
【第四章】 资源 之 4.4 Resource通配符路径 ——跟我学spring3
【第五章】Spring表达式语言 之 5.1 概述 5.2 SpEL基础 ——跟我学spring3
【第五章】Spring表达式语言 之 5.3 SpEL语法 ——跟我学spring3
【第五章】Spring表达式语言 之 5.4在Bean定义中使用EL—跟我学spring3
【第六章】 AOP 之 6.1 AOP基础 ——跟我学spring3
【第六章】 AOP 之 6.2 AOP的HelloWorld ——跟我学spring3
【第六章】 AOP 之 6.3 基于Schema的AOP ——跟我学spring3
【第六章】 AOP 之 6.4 基于@AspectJ的AOP ——跟我学spring3
【第六章】 AOP 之 6.5 AspectJ切入点语法详解 ——跟我学spring3
【第六章】 AOP 之 6.6 通知参数 ——跟我学spring3
【第六章】 AOP 之 6.7 通知顺序 ——跟我学spring3
【第六章】 AOP 之 6.9 代理机制 ——跟我学spring3
【第七章】 对JDBC的支持 之 7.1 概述 ——跟我学spring3
【第七章】 对JDBC的支持 之 7.2 JDBC模板类 ——跟我学spring3
【第七章】 对JDBC的支持 之 7.3 关系数据库操作对象化 ——跟我学spring3
【第七章】 对JDBC的支持 之 7.4 Spring提供的其它帮助 ——跟我学spring3
【第七章】 对JDBC的支持 之 7.5 集成Spring JDBC及最佳实践 ——跟我学spring3
【第八章】 对ORM的支持 之 8.1 概述 ——跟我学spring3
【第八章】 对ORM的支持 之 8.2 集成Hibernate3 ——跟我学spring3
【第八章】 对ORM的支持 之 8.3 集成iBATIS ——跟我学spring3
【第八章】 对ORM的支持 之 8.4 集成JPA ——跟我学spring3
【第九章】 Spring的事务 之 9.1 数据库事务概述 ——跟我学spring3
【第九章】 Spring的事务 之 9.2 事务管理器 ——跟我学spring3
【第九章】 Spring的事务 之 9.3 编程式事务 ——跟我学spring3
【第九章】 Spring的事务 之 9.4 声明式事务 ——跟我学spring3
【第十章】集成其它Web框架 之 10.1 概述 ——跟我学spring3
【第十章】集成其它Web框架 之 10.2 集成Struts1.x ——跟我学spring3
【第十章】集成其它Web框架 之 10.3 集成Struts2.x ——跟我学spring3
【第十章】集成其它Web框架 之 10.4 集成JSF ——跟我学spring3
【第十一章】 SSH集成开发积分商城 之 11.1 概述 ——跟我学spring3
【第十一章】 SSH集成开发积分商城 之 11.2 实现通用层 ——跟我学spring3
【第十一章】 SSH集成开发积分商城 之 11.3 实现积分商城层 ——跟我学spring3
【第十二章】零配置 之 12.1 概述 ——跟我学spring3
【第十二章】零配置 之 12.2 注解实现Bean依赖注入 ——跟我学spring3
【第十二章】零配置 之 12.3 注解实现Bean定义 ——跟我学spring3
【第十二章】零配置 之 12.4 基于Java类定义Bean配置元数据 ——跟我学spring3
【第十二章】零配置 之 12.5 综合示例-积分商城 ——跟我学spring3
【第十三章】 测试 之 13.1 概述 13.2 单元测试 ——跟我学spring3
【第十三章】 测试 之 13.3 集成测试 ——跟我学spring3
SpringMVC + spring3.1.1 + hibernate4.1.0 集成及常见问题总结
• 跟开涛学SpringMVC.pdf (2.6 MB)
• dl.iteye.com/topics/download/dd056e25-1fdb-3844-9d60-a93f6cec7d5e
第一章 Web MVC简介 —— 跟开涛学SpringMVC
发表时间: 2012-07-14 关键字: web, mvc, javaee, spring, 跟开涛学SpringMVC
1.1、Web开发中的请求-响应模型：
在Web世界里，具体步骤如下：
1、 Web浏览器（如IE）发起请求，如访问http://sishuok.com
A web server, such as Tomcat, handles incoming requests by processing them—such as saving new user information—and ultimately generates a response, typically in the form of HTML.
After the web server processes the request, it sends the content back to the web client, typically a browser The client then processes the received content, rendering the HTML to display it to the user.
因此，在Web世界里：
都是Web客户端发起请求，Web服务器接收、处理并产生响应。
Traditional web servers cannot actively notify web clients about content updates However, modern technologies such as server push (like Comet) have emerged to address this limitation.
HTML5 websocket可以实现Web服务器主动通知Web客户端。
In web development, understanding the request/response model is crucial; next, we will explore the standard MVC (Model-View-Controller) architecture.
1.2、标准MVC模型概述
Mô hình MVC là một kiểu kiến trúc giúp tổ chức cấu trúc phát triển một cách hợp lý hơn, không thêm chức năng mới mà chỉ phân tách rõ ràng giữa phần hiển thị và mô hình.
离、流程控制逻辑、业务逻辑调用与展示逻辑分离。如图1-2
首先让我们了解下MVC（Model-View-Controller）三元组的概念：
A model, or data model, serves as a framework for displaying data, encompassing both the data itself and the behaviors associated with it It can be viewed as a domain model or a JavaBean component, which integrates essential data elements and their functionalities.
In modern software architecture, data and behavior are typically separated into distinct components: Value Objects for data management and Service Layers for behavior execution This separation allows models to effectively provide functionalities such as data querying and state updates, encompassing both data handling and business logic.
The view is responsible for displaying the model, essentially representing the user interface that customers interact with and what they wish to see.
The controller receives user requests and delegates processing to the model to effect state changes Once the processing is complete, it returns the model data back to the view.
图，由视图负责展示。 也就是说控制器做了个调度员的工作，。
In a standard MVC framework, the model can actively push data to the view for updates, utilizing the observer design pattern where views are registered to the model for automatic updates However, in web development, the model cannot proactively push updates to the view due to the request-response model inherent in this environment, which limits the ability to automatically refresh the user interface.
Next, let's explore what MVC looks like in the web context, which we refer to as Web MVC to distinguish it from the standard MVC.
The Model-View-Controller (MVC) concept aligns with the standard MVC framework, as referenced in section 1.2 Additionally, we will examine the standard architecture of Web MVC, illustrated in Figure 1-3.
In the Web MVC model, the model cannot proactively push data to the view; instead, the user must send another request to update the view, adhering to the request-response paradigm.
Let's explore the development history of web-based applications, demonstrate how Web MVC is implemented using code, and discuss the reasons for adopting the MVC pattern in web development.
1.4、Web端开发发展历程
此处我们只是简单的叙述比较核心的历程，如图1-4
CGI, or Common Gateway Interface, is a scripting technology utilized on web servers that enables dynamic content generation It commonly employs programming languages such as C or Perl to facilitate communication between the web server and the client.
第二章 Spring MVC入门 —— 跟开涛学SpringMVC
发表时间: 2012-07-16 关键字: REST, IOC, spring, 跟开涛学SpringMVC
2．1、Spring Web MVC是什么
Spring Web MVC is a lightweight web framework based on Java that implements the Web MVC design pattern, promoting a request-driven architecture By employing the MVC framework, it decouples responsibilities within the web layer and utilizes a request-response model The primary goal of Spring Web MVC is to simplify web development, making it easier for developers to create robust web applications.
There are also component-based, event-driven web frameworks, such as Tapestry and JSF, which will not be discussed here.
Spring Web MVC is an implementation of the service-to-worker pattern that allows for optimization The front controller is represented by the DispatcherServlet, while application controllers are divided into handler mappings for processor management and view resolvers for view management The controller interface, which implements the ModelAndView handleRequest(request, response) method, can also be any POJO class It supports localization, theme resolution, and file uploads, offering a highly flexible data validation, formatting, and data binding mechanism Additionally, it provides robust support for convention over configuration, emphasizing a contract-based programming approach.
2．2、Spring Web MVC能帮我们做什么
√让我们能非常简单的设计出干净的Web层和薄薄的Web层；
√进行更简洁的Web层的开发；
√天生与Spring框架集成（如IoC容器、AOP等）；
√提供强大的约定大于配置的契约式编程支持；
√能简单的进行Web层的单元测试；
√支持灵活的URL到页面控制器的映射；
The integration of various view technologies, such as Velocity and FreeMarker, is remarkably straightforward, as model data is not confined to a specific API but is instead stored in a flexible manner.
Model里（Map数据结构实现，因此很容易被其他框架使用）；
Cơ chế xác thực dữ liệu, định dạng và liên kết dữ liệu rất linh hoạt, cho phép sử dụng bất kỳ đối tượng nào để thực hiện liên kết dữ liệu mà không cần phải tuân theo API của một khuôn khổ cụ thể.
√提供一套强大的JSP标签库，简化JSP开发；
√更加简单的异常处理；
√对静态资源的支持；
√支持Restful风格。
2．3、Spring Web MVC架构
The Spring Web MVC framework is a request-driven web framework that utilizes the front controller pattern for its design It dispatches requests to the appropriate page controllers (actions/handlers) based on request mapping rules Let’s take a look at the overall flow of how Spring Web MVC handles requests.
2.3.1、Spring Web MVC处理请求的流程
具体执行步骤如下：
When a user sends a request, it is directed to the front controller, which determines the appropriate page controller to handle the request based on the request information, such as the URL This process involves delegating the request to the selected controller, thereby executing the control logic defined in the previous controller.
Upon receiving a request, the page controller processes the functionality by first gathering and binding the request parameters into an object known as the command object in Spring Web MVC This command object undergoes validation before being delegated to the business object for processing Once the processing is complete, the results are returned.
ModelAndView（模型数据和逻辑视图名）；图2-1中的3、4、5步骤；
The front controller regains control and selects the appropriate view for rendering based on the returned logical view name, while passing the model data for the view rendering process.
The front controller regains control and returns the response to the user, completing the process as illustrated in step 8 of Figure 2-1.
1、 请求如何给前端控制器？
2、 前端控制器如何根据请求信息选择页面控制器进行功能处理？
3、 如何支持多种页面控制器呢？
4、 如何页面控制器如何使用业务对象？
5、 页面控制器如何返回模型数据？
The front controller selects a specific view for rendering based on the logical view name returned by the page controller This process ensures that the appropriate visual representation is provided to the user, enhancing the overall user experience By effectively mapping logical view names to their corresponding views, the front controller streamlines the rendering process, allowing for efficient management of page requests.
7、 不同的视图技术如何使用相应的模型数据？
To address the identified issues, we will explore effective solutions in the following sections.
2.3.2、Spring Web MVC架构
1、Spring Web MVC核心架构图，如图2-2
架构图对应的DispatcherServlet核心代码如下： java代码：
//前端控制器分派方法 protected void doDispatch(HttpServletRequest request, HttpServletResponse response) throws Exception {
HandlerExecutionChain mappedHandler = null; int interceptorIndex = -1; try {
In the code snippet, a ModelAndView object named 'mv' is initialized, and a boolean variable 'errorView' is set to false The code then attempts to determine if the incoming request is a multipart request, such as for file uploads, by utilizing the MultipartResolver to analyze the processedRequest.
In Step 2, the request is mapped to the handler (page controller) using HandlerMapping, as indicated by the line `mappedHandler = getHandler(processedRequest, false)` If the mapped handler is null or does not have a valid handler, the system will invoke the `noHandlerFound` method to handle the processed request and response accordingly.
Step 3 involves processor adaptation, which entails packaging our processor into the appropriate adapter to support various types of processors.
HandlerAdapter ha = getHandlerAdapter(mappedHandler.getHandler());
// 304 Not Modified缓存支持
//此处省略具体代码
// 执行处理器相关的拦截器的预处理
//此处省略具体代码
第三章 DispatcherServlet详解 ——跟开涛学SpringMVC
发表时间: 2012-07-21 关键字: springmvc, spring, mvc
The DispatcherServlet implements the front controller design pattern, serving as a centralized access point for Spring Web MVC It is responsible for delegating responsibilities and integrates seamlessly with the Spring IoC container, allowing users to leverage all the benefits of Spring For further details, please refer to Chapter 2, Figure 2-1.
DispatcherServlet主要用作职责调度工作，本身主要用于控制流程，主要职责如下：
1、文件上传解析，如果请求类型是multipart将通过MultipartResolver进行文件上传解析；
HandlerMapping maps requests to the appropriate handler, returning a HandlerExecutionChain that includes the handler and multiple HandlerInterceptor interceptors.
3、 通过HandlerAdapter支持多种类型的处理器(HandlerExecutionChain
中的处理器)；
4、通过ViewResolver解析逻辑视图名到具体视图实现；
5、本地化解析；
6、渲染具体的视图等；
7、如果执行过程中遇到异常将交给HandlerExceptionResolver来解析。
The DispatcherServlet primarily manages the flow of the application, allowing for easy expansion at each critical point in the process.
3.2、DispatcherServlet在web.xml中的配置
chapter2
1
chapter2
The `load-on-startup` setting indicates that the servlet should be initialized when the container starts, while the `url-pattern` specifies which requests will be handled by Spring Web MVC; using “/” defines the default servlet mapping.
“*.html”表示拦截所有以html为扩展名的请求。
该DispatcherServlet默认使用WebApplicationContext作为上下文，Spring默认配置文件为“/WEB-
INF/[servlet名字]-servlet.xml”。
DispatcherServlet也可以配置自己的初始化参数，覆盖默认配置：
参数 描述 contextClass 实现WebApplicationContext接口的类，当前的servlet用它来创建上下文。如果这
个参数没有指定， 默认使用XmlWebApplicationContext。 contextConfigLocation
The string provided to the context instance specified by contextClass indicates the position of the context This string can be divided into multiple strings using commas as separators to support multiple contexts; in cases of multiple contexts, if the same bean is defined more than once, the latter definition takes precedence The namespace for WebApplicationContext is set to [server-name]-servlet by default.
因此我们可以通过添加初始化参数
I'm sorry, but it seems that the content of the article you provided is not visible Please provide the text you want me to rewrite, and I'll be happy to help!
chapter2
org.springframework.web.servlet.DispatcherServlet
1
contextConfigLocation
classpath:spring-servlet-config.xml
When using the specified configuration, the Spring Web MVC framework will load "classpath:spring-servlet-config.xml" to initialize the context, instead of using "/WEB-INF/[servlet name]-servlet.xml".
3.3、上下文关系
集成Web环境的通用配置：
contextConfigLocation
classpath:spring-common-config.xml, classpath:spring-budget-config.xml
org.springframework.web.context.ContextLoaderListener
The configuration outlined above is a standard setup for integrating Spring with a web environment, primarily used for loading beans beyond the web layer, such as DAOs and services, to facilitate integration with various web frameworks The parameter `contextConfigLocation` specifies the configuration file used for loading beans, while `contextClass` indicates the ApplicationContext implementation class for loading beans, with the default being `WebApplicationContext`.
创建完毕后会将该上下文放在ServletContext： servletContext.setAttribute(
WebApplicationContext.ROOT_WEB_APPLICATION_CONTEXT_ATTRIBUTE, this.context);
ContextLoaderListener初始化的上下文和DispatcherServlet初始化的上下文关系，如图3-1
图3-1 从图中可以看出：
The ContextLoaderListener initializes beans that are shared across the entire application, regardless of the presentation layer technology used, typically including DAO and Service layer beans.
DispatcherServlet初始化的上下文加载的Bean是只对Spring Web MVC有效的Bean，如Controller、
HandlerMapping、HandlerAdapter等等，该初始化上下文应该只加载Web相关组件。
3.4、DispatcherServlet初始化顺序
HttpServletBean extends HttpServlet, which means that its init method is invoked when the web container starts This initialization method primarily serves to set up the servlet's configuration and prepare it for handling requests.
Set the Servlet initialization parameters (init-param) on the component, including contextAttribute, contextClass, namespace, and contextConfigLocation Utilize BeanWrapper to streamline the setting process, making it easier for subsequent usage.
：：：提供给子类初始化扩展点，initServletBean()，该方法由FrameworkServlet覆盖。 public abstract class HttpServletBean extends HttpServlet implements EnvironmentAware{
@Override public final void init() throws ServletException {
//省略部分代码
//1、如下代码的作用是将Servlet初始化参数设置到该组件上
//如contextAttribute、contextClass、namespace、contextConfigLocation； try {
PropertyValues pvs = new ServletConfigPropertyValues(getServletConfig(), this.requiredProperties); BeanWrapper bw = PropertyAccessorFactory.forBeanPropertyAccess(this);
ResourceLoader resourceLoader = new ServletContextResourceLoader(getServletContext()); bw.registerCustomEditor(Resource.class, new ResourceEditor(resourceLoader, this.environment)); initBeanWrapper(bw); bw.setPropertyValues(pvs, true);
//…………省略其他代码 }
//2、提供给子类初始化的扩展点，该方法由FrameworkServlet覆盖 initServletBean(); if (logger.isDebugEnabled()) { logger.debug("Servlet '" + getServletName() + "' configured successfully");
//…………省略其他代码
2、FrameworkServlet继承HttpServletBean，通过initServletBean()进行Web上下文初始化，该方法主要
覆盖一下两件事情：
初始化web上下文；
提供给子类初始化扩展点； public abstract class FrameworkServlet extends HttpServletBean {
@Override protected final void initServletBean() throws ServletException {
//省略部分代码 try {
//1、初始化Web上下文 this.webApplicationContext = initWebApplicationContext();
//2、提供给子类初始化的扩展点 initFrameworkServlet();
//省略部分代码
//ROOT上下文（ContextLoaderListener加载的）
WebApplicationContext rootContext WebApplicationContextUtils.getWebApplicationContext(getServletContext());
In the process of creating a Servlet context, the variable `wac` is assigned the value of `this.webApplicationContext` If `wac` is an instance of `ConfigurableWebApplicationContext`, it is cast to `cwac` The code checks if `cwac` is not active; if it has no parent, it sets the parent context to `rootContext`.
//2、查找已经绑定的上下文 wac = findWebApplicationContext();
//3、如果没有找到相应的上下文，并指定父亲为ContextLoaderListener wac = createWebApplicationContext(rootContext);
//4、刷新上下文（执行一些初始化） onRefresh(wac);
// Publish the context as a servlet context attribute.
String attrName = getServletContextAttributeName(); getServletContext().setAttribute(attrName, wac);
//省略部分代码 } return wac;
The initWebApplicationContext() method indicates that when the ContextLoaderListener loads the context, it will serve as the root context, acting as the parent container for the DispatcherServlet.
The onRefresh() method is invoked to perform some initialization of the container, and this method is implemented by subclasses for further extension.
The DispatcherServlet class extends FrameworkServlet and implements the onRefresh() method, which provides essential configuration for the front controller in a web application.
//实现子类的onRefresh()方法，该方法委托为initStrategies()方法。
@Override protected void onRefresh(ApplicationContext context) { initStrategies(context);