`
yimeng528
  • 浏览: 191334 次
  • 性别: Icon_minigender_1
  • 来自: 北京
社区版块
存档分类
最新评论

基于Spring MVC的Web应用开发(1) - HelloWorld

springmvcspringmvc 
阅读更多

MVC架构

MVC是模型（model），视图（view），控制器（controller）3个单词的首字母缩写。有些应用需要处理用户请求并操纵和显示数据，MVC模式可以简化其实现。该模式由3个组件组成：

 

  • 模型表示用户期望看到的数据。通常情况下，模型由JavaBean组成。
  • 视图负责显示模型。文本编辑器中的视图组件会以恰当的格式显示一段文本，视图在Web应用中会生成客户端浏览器可以解释显示的HTML。
  • 控制器表示逻辑代码，负责处理请求和执行用户的意图。它会构建恰当的模型并将其传入视图进行显示。对Java Web应用来说，控制器多是一个servlet。当然，控制器可以使用任意语言实现，只要web容器支持就行。
Spring MVC介绍
Spring MVC对MVC的实现相当通用。模型就是一个包含数据的简单Map，视图就是一个interface，由它实现显示数据，控制器是Controller接口的实现。
Spring对Web应用下MVC模式的实现基于spring-webmvc下的org.springframework.web.servlet.DispatcherServlet。该Servlet会处理请求并调用恰当的控制元素对请求进行处理。Dispatcher会拦截请求并决定由哪个控制器处理请求。Spring控制器的handling方法会返回一个ModelAndView实例。该实例持有对视图和模型的引用。模型就是一个简单的Map实例，它里面是JavaBean，View接口会显示这些JavaBean。View接口定义了render方法。它遵循这样的原则：View的实现可以是任何东西，只要客户端能对其进行解析就行。
MVC实现
如果要用Spring创建Web应用，需要从基本的web.xml开始，我们在其中指定了DispatcherServlet并为其设定好相应的url-pattern。代码清单如下：
Xml代码 复制代码 收藏代码
  1. <web-appversion="2.5"xmlns="http://java.sun.com/xml/ns/javaee"
  2. xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
  3. xsi:schemaLocation="http://java.sun.com/xml/ns/javaee http://java.sun.com/xml/ns/javaee/web-app_2_5.xsd">
  5. <!-- Processes application requests -->
  6. <servlet>
  7. <servlet-name>appServlet</servlet-name>
  8. <servlet-class>org.springframework.web.servlet.DispatcherServlet</servlet-class>
  9. <init-param>
  10. <param-name>contextConfigLocation</param-name>
  11. <param-value>/WEB-INF/spring/appServlet/servlet-context.xml</param-value>
  12. </init-param>
  13. <load-on-startup>1</load-on-startup>
  14. </servlet>
  16. <servlet-mapping>
  17. <servlet-name>appServlet</servlet-name>
  18. <url-pattern>/</url-pattern>
  19. </servlet-mapping>
  21. <!-- Disables Servlet Container welcome file handling. Needed for compatibility with Servlet 3.0 and Tomcat 7.0 -->
  22. <welcome-file-list>
  23. <welcome-file></welcome-file>
  24. </welcome-file-list>
  26. </web-app>
<web-app version="2.5" xmlns="http://java.sun.com/xml/ns/javaee"
	xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
	xsi:schemaLocation="http://java.sun.com/xml/ns/javaee http://java.sun.com/xml/ns/javaee/web-app_2_5.xsd">

	<!-- Processes application requests -->
	<servlet>
		<servlet-name>appServlet</servlet-name>
		<servlet-class>org.springframework.web.servlet.DispatcherServlet</servlet-class>
		<init-param>
			<param-name>contextConfigLocation</param-name>
			<param-value>/WEB-INF/spring/appServlet/servlet-context.xml</param-value>
		</init-param>
		<load-on-startup>1</load-on-startup>
	</servlet>
	
	<servlet-mapping>
		<servlet-name>appServlet</servlet-name>
		<url-pattern>/</url-pattern>
	</servlet-mapping>
	
	<!-- Disables Servlet Container welcome file handling. Needed for compatibility with Servlet 3.0 and Tomcat 7.0 -->
	<welcome-file-list>
		<welcome-file></welcome-file>
	</welcome-file-list>

</web-app>
上述web.xml文件定义了DispatcherServlet类作为名叫appServlet的Servlet，映射所有请求至该Servlet。
使用处理器映射
对于具体某个请求，Web应用如何知道该调用哪个servlet或者handler实现呢？Spring handler映射就在这里发挥作用了。只需要几步就可以为Spring控制器配置URL映射，因为我们使用的是Spring3.1，@Controller注解专门为此而生。
在具体展示代码前，先说明一下Spring的内部实现原理，Spring使用org.springframework.web.servlet.HandlerMappping这个接口的实现来标识调用的控制器，该接口提供了好多中实现，现在我们只要讲解hello world中需要用到的SimpleUrlHandlerMapping，凭借该handler映射，我们可以在请求中（使用全名和通配符）指定处理该请求的控制器。下列清单展示了一个handler映射的例子：
Java代码 复制代码 收藏代码
  1. package org.springframework.samples.mvc.simple;
  3. import org.springframework.stereotype.Controller;
  4. import org.springframework.web.bind.annotation.RequestMapping;
  5. import org.springframework.web.bind.annotation.ResponseBody;
  7. @Controller
  8. publicclass SimpleController {
  10. @RequestMapping("/simple")
  11. @ResponseBody
  12. public String simple() {
  13. return"Hello world!";
  14. }
  16. } 
package org.springframework.samples.mvc.simple;

import org.springframework.stereotype.Controller;
import org.springframework.web.bind.annotation.RequestMapping;
import org.springframework.web.bind.annotation.ResponseBody;

@Controller
public class SimpleController {

	@RequestMapping("/simple")
	@ResponseBody
	public String simple() {
		return "Hello world!";
	}
	
}
Spring控制器
控制器负责处理请求：根据request构建model并将其传到view以进行显示。
DispatcherServlet有一个List类型的handlerAdapters属性，它可用来指定你想用的HandlerAdapter实现，如果这个属性值为null，就会使用默认的策略。这句话暂时不明白没关系，下文会有详细解读。
上面的代码清单其实已经继承一个控制器实现。在启动的时候我们会注意到有这样的输出日志：
Log代码 复制代码 收藏代码
  1. INFO: Mapped URL path [/simple] onto handler 'simpleController'
  2. INFO: Mapped URL path [/simple.*] onto handler 'simpleController'
  3. INFO: Mapped URL path [/simple/] onto handler 'simpleController'
INFO: Mapped URL path [/simple] onto handler 'simpleController'
INFO: Mapped URL path [/simple.*] onto handler 'simpleController'
INFO: Mapped URL path [/simple/] onto handler 'simpleController'
因为我们在web.xml中做了全局性的URL通配符，所以这里Spring“智能”的为我们的@RequestMapping("/simple")映射好三种URL（如何只保留其中一种，以后再讲）。
视图
hello world并没有视图，因为我们使用了@ResponseBody注解，该注解直接将控制器中的返回值绑定到web响应体里，如果返回的是字符串，那么该字符串就显示在浏览器上，而这也就是我们想要的。上面例子的结果是将文本hello world写入http响应流中。下面将spring官方手册中有关@ResponseBody的解释翻译一下：
翻译代码 复制代码 收藏代码
  1. @ResponseBody注解和@RequestBody相似。这个注解可以放在方法上，表明返回的类型应该是可以直接写入到HTTP响应体里的（Model中不会放置该值，该值也不会被转成一个view名字）。 
@ResponseBody注解和@RequestBody相似。这个注解可以放在方法上，表明返回的类型应该是可以直接写入到HTTP响应体里的（Model中不会放置该值，该值也不会被转成一个view名字）。
视图的深入讲解将在以后逐步讲到。
至此，一个简单的hello world就讲完了，但是我们还是有疑问，这些只是表面现象，Spring底层到底是运作的呢？
首先我们来看
Xml代码 复制代码 收藏代码
  1. <servlet>
  2. <servlet-name>appServlet</servlet-name>
  3. <servlet-class>org.springframework.web.servlet.DispatcherServlet</servlet-class>
  4. <init-param>
  5. <param-name>contextConfigLocation</param-name>
  6. <param-value>/WEB-INF/spring/appServlet/servlet-context.xml</param-value>
  7. </init-param>
  8. <load-on-startup>1</load-on-startup>
  9. </servlet>
<servlet>
		<servlet-name>appServlet</servlet-name>
		<servlet-class>org.springframework.web.servlet.DispatcherServlet</servlet-class>
		<init-param>
			<param-name>contextConfigLocation</param-name>
			<param-value>/WEB-INF/spring/appServlet/servlet-context.xml</param-value>
		</init-param>
		<load-on-startup>1</load-on-startup>
	</servlet>
系统启动时会加载DispatcherServlet这个Servlet，深入看一下：
Java代码 复制代码 收藏代码
  1. publicclass DispatcherServlet extends FrameworkServlet 
public class DispatcherServlet extends FrameworkServlet
Java代码 复制代码 收藏代码
  1. publicabstractclass FrameworkServlet extends HttpServletBean 
public abstract class FrameworkServlet extends HttpServletBean
Java代码 复制代码 收藏代码
  1. publicabstractclass HttpServletBean extends HttpServlet implements EnvironmentAware 
public abstract class HttpServletBean extends HttpServlet implements EnvironmentAware

可见DispatcherServlet是继承了javax.servlet.http.HttpServlet的一个Servlet，既然是一个Servlet，则必然有

 

Java代码 复制代码 收藏代码
  1. @Override
  2. publicfinalvoid init() throws ServletException;
  4. @Override
  5. protectedfinalvoid doGet(HttpServletRequest request, HttpServletResponse response)
  6. throws ServletException, IOException;
  8. @Override
  9. protectedfinalvoid doPost(HttpServletRequest request, HttpServletResponse response)
  10. throws ServletException, IOException;
  12. @Override
  13. protectedvoid doService(HttpServletRequest request, HttpServletResponse response) throws Exception; 
@Override
public final void init() throws ServletException;

@Override
protected final void doGet(HttpServletRequest request, HttpServletResponse response)
			throws ServletException, IOException;

@Override
protected final void doPost(HttpServletRequest request, HttpServletResponse response)
			throws ServletException, IOException;

@Override
protected void doService(HttpServletRequest request, HttpServletResponse response) throws Exception;

 

这几个方法的实现，我们一个一个看：

init()方法在HttpServletBean中实现，doGet和doPost方法在FrameworkServlet中实现，doService()方法在DispatcherServlet中实现。

根据Servlet规范，一个Servlet启动的时候需要执行init()方法，一个请求来了首先判断是Get还Post方式提交，Get方式提交的执行doGet()方法，Post方式提交的执行doPost()方法。然后在doGet()和doPost()方法中可调用doService()方法，SpringMVC完全参照此规范。

在init()中，HttpServletBean执行

 

Java代码 复制代码 收藏代码
  1. protectedvoid initServletBean() throws ServletException {
  2. } 
protected void initServletBean() throws ServletException {
	}

 

讲具体的实现交给FrameworkServlt重载的方法完成

 

Java代码 复制代码 收藏代码
  1. @Override
  2. protectedfinalvoid initServletBean() throws ServletException {
  3. System.out.println("使用servlet上下文记录日志");
  4. getServletContext().log("Initializing Spring FrameworkServlet '" + getServletName() + "'");
  5. if (this.logger.isInfoEnabled()) {
  6. this.logger.info("FrameworkServlet '" + getServletName() + "': initialization started");
  7. }
  8. long startTime = System.currentTimeMillis();
  9. System.out.println("启动时间：[" + startTime + "]");
  11. try {
  12. System.out.println("initWebApplicationContext()");
  13. this.webApplicationContext = initWebApplicationContext();
  14. System.out.println("initFrameworkServlet()，这是一个空实现");
  15. initFrameworkServlet();
  16. }
  17. catch (ServletException ex) {
  18. this.logger.error("Context initialization failed", ex);
  19. throw ex;
  20. }
  21. catch (RuntimeException ex) {
  22. this.logger.error("Context initialization failed", ex);
  23. throw ex;
  24. }
  26. if (this.logger.isInfoEnabled()) {
  27. long elapsedTime = System.currentTimeMillis() - startTime;
  28. System.out.println("结束时间：[" + elapsedTime + "]");
  29. this.logger.info("FrameworkServlet '" + getServletName() + "': initialization completed in " +
  30. elapsedTime + " ms");
  31. }
  32. } 
@Override
	protected final void initServletBean() throws ServletException {
System.out.println("使用servlet上下文记录日志");
		getServletContext().log("Initializing Spring FrameworkServlet '" + getServletName() + "'");
		if (this.logger.isInfoEnabled()) {
			this.logger.info("FrameworkServlet '" + getServletName() + "': initialization started");
		}
		long startTime = System.currentTimeMillis();
System.out.println("启动时间：[" + startTime + "]");

		try {
System.out.println("initWebApplicationContext()");
			this.webApplicationContext = initWebApplicationContext();
System.out.println("initFrameworkServlet()，这是一个空实现");
			initFrameworkServlet();
		}
		catch (ServletException ex) {
			this.logger.error("Context initialization failed", ex);
			throw ex;
		}
		catch (RuntimeException ex) {
			this.logger.error("Context initialization failed", ex);
			throw ex;
		}

		if (this.logger.isInfoEnabled()) {
			long elapsedTime = System.currentTimeMillis() - startTime;
System.out.println("结束时间：[" + elapsedTime + "]");
			this.logger.info("FrameworkServlet '" + getServletName() + "': initialization completed in " +
					elapsedTime + " ms");
		}
	}

 

该方法会记录启动耗费的时间，也就时我们在启动项目时在控制台看到的时间，这里还解释了，为什么输出启动耗时的日志一般是红色的。

在该方法中执行了initWebApplicationContext()方法，进入该方法

 

Java代码 复制代码 收藏代码
  1. protected WebApplicationContext initWebApplicationContext() {
  2. //System.out.println("使用WebApplicationContextUtils工具类得到WebApplicatonContext");
  3. WebApplicationContext rootContext =
  4. WebApplicationContextUtils.getWebApplicationContext(getServletContext());
  5. WebApplicationContext wac = null;
  7. //System.out.println("判断webApplicationContext是否为null");
  8. if (this.webApplicationContext != null) {
  9. //System.out.println("webApplicationContext非空！");
  10. // A context instance was injected at construction time -> use it
  11. wac = this.webApplicationContext;
  12. if (wac instanceof ConfigurableWebApplicationContext) {
  13. ConfigurableWebApplicationContext cwac = (ConfigurableWebApplicationContext) wac;
  14. if (!cwac.isActive()) {
  15. // The context has not yet been refreshed -> provide services such as
  16. // setting the parent context, setting the application context id, etc
  17. if (cwac.getParent() == null) {
  18. // The context instance was injected without an explicit parent -> set
  19. // the root application context (if any; may be null) as the parent
  20. cwac.setParent(rootContext);
  21. }
  22. configureAndRefreshWebApplicationContext(cwac);
  23. }
  24. }
  25. }
  26. //System.out.println("判断wac是否为null");
  27. if (wac == null) {
  28. //System.out.println("was为空");
  29. // No context instance was injected at construction time -> see if one
  30. // has been registered in the servlet context. If one exists, it is assumed
  31. // that the parent context (if any) has already been set and that the
  32. // user has performed any initialization such as setting the context id
  33. wac = findWebApplicationContext();
  34. }
  35. //System.out.println("再次判断wac是否为null");
  36. if (wac == null) {
  37. System.out.println("wac还为空");
  38. System.out.println("No context instance is defined for this servlet -> create a local one");
  39. // No context instance is defined for this servlet -> create a local one
  40. wac = createWebApplicationContext(rootContext);
  41. }
  43. System.out.println("this.refreshEventReceived:[" + this.refreshEventReceived + "]");
  44. if (!this.refreshEventReceived) {
  45. System.out.println("onRefresh");
  46. // Either the context is not a ConfigurableApplicationContext with refresh
  47. // support or the context injected at construction time had already been
  48. // refreshed -> trigger initial onRefresh manually here.
  49. onRefresh(wac);
  50. }
  52. System.out.println("this.publishContext:[" + this.publishContext + "]");
  53. if (this.publishContext) {
  54. System.out.println("Publish the context as a servlet context attribute.");
  55. // Publish the context as a servlet context attribute.
  56. String attrName = getServletContextAttributeName();
  57. getServletContext().setAttribute(attrName, wac);
  58. if (this.logger.isDebugEnabled()) {
  59. this.logger.debug("Published WebApplicationContext of servlet '" + getServletName() +
  60. "' as ServletContext attribute with name [" + attrName + "]");
  61. }
  62. }
  64. return wac;
  65. } 
protected WebApplicationContext initWebApplicationContext() {
//System.out.println("使用WebApplicationContextUtils工具类得到WebApplicatonContext");
		WebApplicationContext rootContext =
				WebApplicationContextUtils.getWebApplicationContext(getServletContext());
		WebApplicationContext wac = null;

//System.out.println("判断webApplicationContext是否为null");
		if (this.webApplicationContext != null) {
//System.out.println("webApplicationContext非空！");
			// A context instance was injected at construction time -> use it
			wac = this.webApplicationContext;
			if (wac instanceof ConfigurableWebApplicationContext) {
				ConfigurableWebApplicationContext cwac = (ConfigurableWebApplicationContext) wac;
				if (!cwac.isActive()) {
					// The context has not yet been refreshed -> provide services such as
					// setting the parent context, setting the application context id, etc
					if (cwac.getParent() == null) {
						// The context instance was injected without an explicit parent -> set
						// the root application context (if any; may be null) as the parent
						cwac.setParent(rootContext);
					}
					configureAndRefreshWebApplicationContext(cwac);
				}
			}
		}
//System.out.println("判断wac是否为null");
		if (wac == null) {
//System.out.println("was为空");
			// No context instance was injected at construction time -> see if one
			// has been registered in the servlet context. If one exists, it is assumed
			// that the parent context (if any) has already been set and that the
			// user has performed any initialization such as setting the context id
			wac = findWebApplicationContext();
		}
//System.out.println("再次判断wac是否为null");
		if (wac == null) {
System.out.println("wac还为空");
System.out.println("No context instance is defined for this servlet -> create a local one");
			// No context instance is defined for this servlet -> create a local one
			wac = createWebApplicationContext(rootContext);
		}

System.out.println("this.refreshEventReceived:[" + this.refreshEventReceived + "]");
		if (!this.refreshEventReceived) {
System.out.println("onRefresh");
			// Either the context is not a ConfigurableApplicationContext with refresh
			// support or the context injected at construction time had already been
			// refreshed -> trigger initial onRefresh manually here.
			onRefresh(wac);
		}

System.out.println("this.publishContext:[" + this.publishContext + "]");
		if (this.publishContext) {
System.out.println("Publish the context as a servlet context attribute.");
			// Publish the context as a servlet context attribute.
			String attrName = getServletContextAttributeName();
			getServletContext().setAttribute(attrName, wac);
			if (this.logger.isDebugEnabled()) {
				this.logger.debug("Published WebApplicationContext of servlet '" + getServletName() +
						"' as ServletContext attribute with name [" + attrName + "]");
			}
		}

		return wac;
	}

 

发现很长，但其实有用的只有wac = createWebApplicationContext(rootContext);在进入这个方法

 

Java代码 复制代码 收藏代码
  1. protected WebApplicationContext createWebApplicationContext(ApplicationContext parent) {
  2. System.out.println("createWebApplicationContext");
  3. Class<?> contextClass = getContextClass();
  4. if (this.logger.isDebugEnabled()) {
  5. this.logger.debug("Servlet with name '" + getServletName() +
  6. "' will try to create custom WebApplicationContext context of class '" +
  7. contextClass.getName() + "'" + ", using parent context [" + parent + "]");
  8. }
  9. if (!ConfigurableWebApplicationContext.class.isAssignableFrom(contextClass)) {
  10. thrownew ApplicationContextException(
  11. "Fatal initialization error in servlet with name '" + getServletName() +
  12. "': custom WebApplicationContext class [" + contextClass.getName() +
  13. "] is not of type ConfigurableWebApplicationContext");
  14. }
  15. System.out.println("初始化Bean开始");
  16. ConfigurableWebApplicationContext wac =
  17. (ConfigurableWebApplicationContext) BeanUtils.instantiateClass(contextClass);
  18. System.out.println("初始化Bean结束");
  20. wac.setParent(parent);
  21. wac.setConfigLocation(getContextConfigLocation());
  23. System.out.println("configureAndRefreshWebApplicationContext开始");
  24. configureAndRefreshWebApplicationContext(wac);
  25. System.out.println("configureAndRefreshWebApplicationContext结束");
  27. return wac;
  28. } 
protected WebApplicationContext createWebApplicationContext(ApplicationContext parent) {
System.out.println("createWebApplicationContext");
		Class<?> contextClass = getContextClass();
		if (this.logger.isDebugEnabled()) {
			this.logger.debug("Servlet with name '" + getServletName() +
					"' will try to create custom WebApplicationContext context of class '" +
					contextClass.getName() + "'" + ", using parent context [" + parent + "]");
		}
		if (!ConfigurableWebApplicationContext.class.isAssignableFrom(contextClass)) {
			throw new ApplicationContextException(
					"Fatal initialization error in servlet with name '" + getServletName() +
					"': custom WebApplicationContext class [" + contextClass.getName() +
					"] is not of type ConfigurableWebApplicationContext");
		}
System.out.println("初始化Bean开始");
		ConfigurableWebApplicationContext wac =
				(ConfigurableWebApplicationContext) BeanUtils.instantiateClass(contextClass);
System.out.println("初始化Bean结束");		

		wac.setParent(parent);
		wac.setConfigLocation(getContextConfigLocation());

System.out.println("configureAndRefreshWebApplicationContext开始");
		configureAndRefreshWebApplicationContext(wac);
System.out.println("configureAndRefreshWebApplicationContext结束");

		return wac;
	}

 

于是我们就看到了有点眼熟的

 

Java代码 复制代码 收藏代码
  1. ConfigurableWebApplicationContext wac =
  2. (ConfigurableWebApplicationContext) BeanUtils.instantiateClass(contextClass); 
ConfigurableWebApplicationContext wac =
				(ConfigurableWebApplicationContext) BeanUtils.instantiateClass(contextClass);

 

这个方法就开始初始化我们servlet上下文即spring配置文件中的bean了。

我们的配置文件中servlet-context.xml只要一行

 

Xml代码 复制代码 收藏代码
  1. <beans:importresource="controllers.xml"/>
<beans:import resource="controllers.xml" />

 

而controllers.xml中

 

Xml代码 复制代码 收藏代码
  1. <context:component-scanbase-package="org.springframework.samples.mvc"/>
<context:component-scan base-package="org.springframework.samples.mvc" />

 

含义是扫描指定包下面所有带有注解的类，并将他们初始化。上面已经列出了带有@Controller注解的SimpleController类，于是Spring默认将这个bean的名字命名为simpleController（类名首字母小写），然后发现有一个方法带有@RequestMapping，Spring便通过org.springframework.web.servlet.mvc.annotation.DefaultAnnotationHandlerMapping创建URL和控制器的映射(handlerMapping)，具体过程可看如下日志：

 

Log代码 复制代码 收藏代码
  1. DEBUG: org.springframework.web.servlet.mvc.annotation.DefaultAnnotationHandlerMapping - Looking for URL mappings in application context: WebApplicationContext for namespace 'appServlet-servlet': startup date [Fri Mar 1605:36:03 CST 2012]; root of context hierarchy
  2. DEBUG: org.springframework.beans.factory.support.DefaultListableBeanFactory - Returning cached instance of singleton bean 'simpleController'
  3. 将一个URL路径映射到一个handler上
  4. INFO : org.springframework.web.servlet.mvc.annotation.DefaultAnnotationHandlerMapping - Mapped URL path [/simple] onto handler 'simpleController'
  5. DEBUG: org.springframework.beans.factory.support.DefaultListableBeanFactory - Returning cached instance of singleton bean 'simpleController'
  6. 将一个URL路径映射到一个handler上
  7. INFO : org.springframework.web.servlet.mvc.annotation.DefaultAnnotationHandlerMapping - Mapped URL path [/simple.*] onto handler 'simpleController'
  8. DEBUG: org.springframework.beans.factory.support.DefaultListableBeanFactory - Returning cached instance of singleton bean 'simpleController'
  9. 将一个URL路径映射到一个handler上
  10. INFO : org.springframework.web.servlet.mvc.annotation.DefaultAnnotationHandlerMapping - Mapped URL path [/simple/] onto handler 'simpleController'
DEBUG: org.springframework.web.servlet.mvc.annotation.DefaultAnnotationHandlerMapping - Looking for URL mappings in application context: WebApplicationContext for namespace 'appServlet-servlet': startup date [Fri Mar 16 05:36:03 CST 2012]; root of context hierarchy
DEBUG: org.springframework.beans.factory.support.DefaultListableBeanFactory - Returning cached instance of singleton bean 'simpleController'
将一个URL路径映射到一个handler上
INFO : org.springframework.web.servlet.mvc.annotation.DefaultAnnotationHandlerMapping - Mapped URL path [/simple] onto handler 'simpleController'
DEBUG: org.springframework.beans.factory.support.DefaultListableBeanFactory - Returning cached instance of singleton bean 'simpleController'
将一个URL路径映射到一个handler上
INFO : org.springframework.web.servlet.mvc.annotation.DefaultAnnotationHandlerMapping - Mapped URL path [/simple.*] onto handler 'simpleController'
DEBUG: org.springframework.beans.factory.support.DefaultListableBeanFactory - Returning cached instance of singleton bean 'simpleController'
将一个URL路径映射到一个handler上
INFO : org.springframework.web.servlet.mvc.annotation.DefaultAnnotationHandlerMapping - Mapped URL path [/simple/] onto handler 'simpleController'

 

URL到控制器的映射创建完了，剩下的便是处理器代理了（handlerAdapter），前文提到了，DispatcherServlet有一个List类型的handlerAdapters，如果为null，系统将使用默认策略。这个默认策略体现在DispatcherServlet的这个方法中

 

Java代码 复制代码 收藏代码
  1. /**
  2. * Initialize the HandlerAdapters used by this class.
  3. * <p>If no HandlerAdapter beans are defined in the BeanFactory for this namespace,
  4. * we default to SimpleControllerHandlerAdapter.
  5. */
  6. privatevoid initHandlerAdapters(ApplicationContext context) {
  7. this.handlerAdapters = null;
  9. if (this.detectAllHandlerAdapters) {
  10. // Find all HandlerAdapters in the ApplicationContext, including ancestor contexts.
  11. Map<String, HandlerAdapter> matchingBeans =
  12. BeanFactoryUtils.beansOfTypeIncludingAncestors(context, HandlerAdapter.class, true, false);
  13. if (!matchingBeans.isEmpty()) {
  14. this.handlerAdapters = new ArrayList<HandlerAdapter>(matchingBeans.values());
  15. // We keep HandlerAdapters in sorted order.
  16. OrderComparator.sort(this.handlerAdapters);
  17. }
  18. }
  19. else {
  20. try {
  21. HandlerAdapter ha = context.getBean(HANDLER_ADAPTER_BEAN_NAME, HandlerAdapter.class);
  22. this.handlerAdapters = Collections.singletonList(ha);
  23. }
  24. catch (NoSuchBeanDefinitionException ex) {
  25. // Ignore, we'll add a default HandlerAdapter later.
  26. }
  27. }
  29. // Ensure we have at least some HandlerAdapters, by registering
  30. // default HandlerAdapters if no other adapters are found.
  31. if (this.handlerAdapters == null) {
  32. System.out.println("确保我们有一些handlerAdapters");
  33. this.handlerAdapters = getDefaultStrategies(context, HandlerAdapter.class);
  34. if (logger.isDebugEnabled()) {
  35. logger.debug("No HandlerAdapters found in servlet '" + getServletName() + "': using default");
  36. }
  37. }
  38. } 
/**
	 * Initialize the HandlerAdapters used by this class.
	 * <p>If no HandlerAdapter beans are defined in the BeanFactory for this namespace,
	 * we default to SimpleControllerHandlerAdapter.
	 */
	private void initHandlerAdapters(ApplicationContext context) {
		this.handlerAdapters = null;

		if (this.detectAllHandlerAdapters) {
			// Find all HandlerAdapters in the ApplicationContext, including ancestor contexts.
			Map<String, HandlerAdapter> matchingBeans =
					BeanFactoryUtils.beansOfTypeIncludingAncestors(context, HandlerAdapter.class, true, false);
			if (!matchingBeans.isEmpty()) {
				this.handlerAdapters = new ArrayList<HandlerAdapter>(matchingBeans.values());
				// We keep HandlerAdapters in sorted order.
				OrderComparator.sort(this.handlerAdapters);
			}
		}
		else {
			try {
				HandlerAdapter ha = context.getBean(HANDLER_ADAPTER_BEAN_NAME, HandlerAdapter.class);
				this.handlerAdapters = Collections.singletonList(ha);
			}
			catch (NoSuchBeanDefinitionException ex) {
				// Ignore, we'll add a default HandlerAdapter later.
			}
		}

		// Ensure we have at least some HandlerAdapters, by registering
		// default HandlerAdapters if no other adapters are found.
		if (this.handlerAdapters == null) {
System.out.println("确保我们有一些handlerAdapters");
			this.handlerAdapters = getDefaultStrategies(context, HandlerAdapter.class);
			if (logger.isDebugEnabled()) {
				logger.debug("No HandlerAdapters found in servlet '" + getServletName() + "': using default");
			}
		}
	}

 

这个默认策略会给我们三个HandlerAdapter，具体日志：

 

Java代码 复制代码 收藏代码
  1. DEBUG: org.springframework.beans.factory.support.DefaultListableBeanFactory - Finished creating instance of bean 'org.springframework.web.servlet.mvc.HttpRequestHandlerAdapter'
  2. DEBUG: org.springframework.beans.factory.support.DefaultListableBeanFactory - Finished creating instance of bean 'org.springframework.web.servlet.mvc.SimpleControllerHandlerAdapter'
  3. DEBUG: org.springframework.beans.factory.support.DefaultListableBeanFactory - Finished creating instance of bean 'org.springframework.web.servlet.mvc.annotation.AnnotationMethodHandlerAdapter'
DEBUG: org.springframework.beans.factory.support.DefaultListableBeanFactory - Finished creating instance of bean 'org.springframework.web.servlet.mvc.HttpRequestHandlerAdapter'
DEBUG: org.springframework.beans.factory.support.DefaultListableBeanFactory - Finished creating instance of bean 'org.springframework.web.servlet.mvc.SimpleControllerHandlerAdapter'
DEBUG: org.springframework.beans.factory.support.DefaultListableBeanFactory - Finished creating instance of bean 'org.springframework.web.servlet.mvc.annotation.AnnotationMethodHandlerAdapter'

 

至此，init()可以算是执行完了（当然为了简化，还有一些无关大局的细节略去没有讲），我们的Servlet，也就是项目就运行起来了。

下面讲解请求部分

先来看一段浏览器发出请求后，服务端的记录的日志

 

Log代码 复制代码 收藏代码
  1. FrameworkServlet doGet
  2. TRACE: org.springframework.web.servlet.DispatcherServlet - Bound request context to thread: [GET /web/simple]@902324502 org.eclipse.jetty.server.Request@35c86116
  3. doService
  4. DEBUG: org.springframework.web.servlet.DispatcherServlet - DispatcherServlet with name 'appServlet' processing GET request for [/web/simple]
  5. doDispatch
  6. Determine handler for the current request.
  7. TRACE: org.springframework.web.servlet.DispatcherServlet - Testing handler map [org.springframework.web.servlet.handler.BeanNameUrlHandlerMapping@20d1fa4] in DispatcherServlet with name 'appServlet'
  8. TRACE: org.springframework.web.servlet.handler.BeanNameUrlHandlerMapping - No handler mapping found for [/simple]
  9. TRACE: org.springframework.web.servlet.DispatcherServlet - Testing handler map [org.springframework.web.servlet.mvc.annotation.DefaultAnnotationHandlerMapping@5b33a7af] in DispatcherServlet with name 'appServlet'
  10. DEBUG: org.springframework.web.servlet.mvc.annotation.DefaultAnnotationHandlerMapping - Mapping [/simple] to HandlerExecutionChain with handler [org.springframework.samples.mvc.simple.SimpleController@573b7064] and 1 interceptor
  11. Determine handler adapter for the current request.
  12. TRACE: org.springframework.web.servlet.DispatcherServlet - Testing handler adapter [org.springframework.web.servlet.mvc.HttpRequestHandlerAdapter@557ce3bb]
  13. TRACE: org.springframework.web.servlet.DispatcherServlet - Testing handler adapter [org.springframework.web.servlet.mvc.SimpleControllerHandlerAdapter@6996a298]
  14. TRACE: org.springframework.web.servlet.DispatcherServlet - Testing handler adapter [org.springframework.web.servlet.mvc.annotation.AnnotationMethodHandlerAdapter@783b67a7]
  15. Process last-modified header, if supported by the handler.
  16. DEBUG: org.springframework.web.servlet.DispatcherServlet - Last-Modified value for [/web/simple] is: -1
  17. Apply preHandle methods of registered interceptors.
  18. Actually invoke the handler.
  19. class org.springframework.web.servlet.mvc.annotation.AnnotationMethodHandlerAdapter
  20. invokeHandlerMethod
  21. 真正处理
  22. DEBUG: org.springframework.web.bind.annotation.support.HandlerMethodInvoker - Invoking request handler method: public java.lang.String org.springframework.samples.mvc.simple.SimpleController.simple()
  23. result:[Hello world!]
  24. getModelAndView[class java.lang.String]
  25. 原来进入了这个分支
  26. OK搞定
  27. 具体输出数据
  28. DEBUG: org.springframework.web.servlet.mvc.annotation.AnnotationMethodHandlerAdapter - Written [Hello world!] as "text/html" using [org.springframework.http.converter.StringHttpMessageConverter@6b7de5ce]
  29. 返回mv为空，假设handler已经处理完了
  30. Do we need view name translation?
  31. Apply postHandle methods of registered interceptors.
  32. DEBUG: org.springframework.web.servlet.DispatcherServlet - Null ModelAndView returned to DispatcherServlet with name 'appServlet': assuming HandlerAdapter completed request handling
  33. Trigger after-completion for successful outcome.
  34. [1]
  35. TRACE: org.springframework.web.servlet.DispatcherServlet - Cleared thread-bound request context: [GET /web/simple]@902324502 org.eclipse.jetty.server.Request@35c86116
  36. DEBUG: org.springframework.web.servlet.DispatcherServlet - Successfully completed request
  37. TRACE: org.springframework.web.context.support.XmlWebApplicationContext - Publishing event in WebApplicationContext for namespace 'appServlet-servlet': ServletRequestHandledEvent: url=[/web/simple]; client=[0:0:0:0:0:0:0:1%0]; method=[GET]; servlet=[appServlet]; session=[null]; user=[null]; time=[154ms]; status=[OK] 
FrameworkServlet doGet
TRACE: org.springframework.web.servlet.DispatcherServlet - Bound request context to thread: [GET /web/simple]@902324502 org.eclipse.jetty.server.Request@35c86116
doService
DEBUG: org.springframework.web.servlet.DispatcherServlet - DispatcherServlet with name 'appServlet' processing GET request for [/web/simple]
doDispatch
Determine handler for the current request.
TRACE: org.springframework.web.servlet.DispatcherServlet - Testing handler map [org.springframework.web.servlet.handler.BeanNameUrlHandlerMapping@20d1fa4] in DispatcherServlet with name 'appServlet'
TRACE: org.springframework.web.servlet.handler.BeanNameUrlHandlerMapping - No handler mapping found for [/simple]
TRACE: org.springframework.web.servlet.DispatcherServlet - Testing handler map [org.springframework.web.servlet.mvc.annotation.DefaultAnnotationHandlerMapping@5b33a7af] in DispatcherServlet with name 'appServlet'
DEBUG: org.springframework.web.servlet.mvc.annotation.DefaultAnnotationHandlerMapping - Mapping [/simple] to HandlerExecutionChain with handler [org.springframework.samples.mvc.simple.SimpleController@573b7064] and 1 interceptor
Determine handler adapter for the current request.
TRACE: org.springframework.web.servlet.DispatcherServlet - Testing handler adapter [org.springframework.web.servlet.mvc.HttpRequestHandlerAdapter@557ce3bb]
TRACE: org.springframework.web.servlet.DispatcherServlet - Testing handler adapter [org.springframework.web.servlet.mvc.SimpleControllerHandlerAdapter@6996a298]
TRACE: org.springframework.web.servlet.DispatcherServlet - Testing handler adapter [org.springframework.web.servlet.mvc.annotation.AnnotationMethodHandlerAdapter@783b67a7]
Process last-modified header, if supported by the handler.
DEBUG: org.springframework.web.servlet.DispatcherServlet - Last-Modified value for [/web/simple] is: -1
Apply preHandle methods of registered interceptors.
Actually invoke the handler.
class org.springframework.web.servlet.mvc.annotation.AnnotationMethodHandlerAdapter
invokeHandlerMethod
真正处理
DEBUG: org.springframework.web.bind.annotation.support.HandlerMethodInvoker - Invoking request handler method: public java.lang.String org.springframework.samples.mvc.simple.SimpleController.simple()
result:[Hello world!]
getModelAndView[class java.lang.String]
原来进入了这个分支
OK搞定
具体输出数据
DEBUG: org.springframework.web.servlet.mvc.annotation.AnnotationMethodHandlerAdapter - Written [Hello world!] as "text/html" using [org.springframework.http.converter.StringHttpMessageConverter@6b7de5ce]
返回mv为空，假设handler已经处理完了
Do we need view name translation?
Apply postHandle methods of registered interceptors.
DEBUG: org.springframework.web.servlet.DispatcherServlet - Null ModelAndView returned to DispatcherServlet with name 'appServlet': assuming HandlerAdapter completed request handling
Trigger after-completion for successful outcome.
[1]
TRACE: org.springframework.web.servlet.DispatcherServlet - Cleared thread-bound request context: [GET /web/simple]@902324502 org.eclipse.jetty.server.Request@35c86116
DEBUG: org.springframework.web.servlet.DispatcherServlet - Successfully completed request
TRACE: org.springframework.web.context.support.XmlWebApplicationContext - Publishing event in WebApplicationContext for namespace 'appServlet-servlet': ServletRequestHandledEvent: url=[/web/simple]; client=[0:0:0:0:0:0:0:1%0]; method=[GET]; servlet=[appServlet]; session=[null]; user=[null]; time=[154ms]; status=[OK]

 

我们来详细分析一下，请求上来时，首先进入FrameworkServlet的doGet方法，然后调用

 

Java代码 复制代码 收藏代码
  1. /**
  2. * Process this request, publishing an event regardless of the outcome.
  3. * <p>The actual event handling is performed by the abstract
  4. * {@link #doService} template method.
  5. */
  6. protectedfinalvoid processRequest(HttpServletRequest request, HttpServletResponse response)
  7. throws ServletException, IOException {
  9. long startTime = System.currentTimeMillis();
  10. Throwable failureCause = null;
  12. // Expose current LocaleResolver and request as LocaleContext.
  13. LocaleContext previousLocaleContext = LocaleContextHolder.getLocaleContext();
  14. LocaleContextHolder.setLocaleContext(buildLocaleContext(request), this.threadContextInheritable);
  16. // Expose current RequestAttributes to current thread.
  17. RequestAttributes previousRequestAttributes = RequestContextHolder.getRequestAttributes();
  18. ServletRequestAttributes requestAttributes = null;
  19. if (previousRequestAttributes == null || previousRequestAttributes.getClass().equals(ServletRequestAttributes.class)) {
  20. requestAttributes = new ServletRequestAttributes(request);
  21. RequestContextHolder.setRequestAttributes(requestAttributes, this.threadContextInheritable);
  22. }
  24. if (logger.isTraceEnabled()) {
  25. logger.trace("Bound request context to thread: " + request);
  26. }
  28. try {
  29. doService(request, response);
  30. }
  31. catch (ServletException ex) {
  32. failureCause = ex;
  33. throw ex;
  34. }
  35. catch (IOException ex) {
  36. failureCause = ex;
  37. throw ex;
  38. }
  39. catch (Throwable ex) {
  40. failureCause = ex;
  41. thrownew NestedServletException("Request processing failed", ex);
  42. }
  44. finally {
  45. // Clear request attributes and reset thread-bound context.
  46. LocaleContextHolder.setLocaleContext(previousLocaleContext, this.threadContextInheritable);
  47. if (requestAttributes != null) {
  48. RequestContextHolder.setRequestAttributes(previousRequestAttributes, this.threadContextInheritable);
  49. requestAttributes.requestCompleted();
  50. }
  51. if (logger.isTraceEnabled()) {
  52. logger.trace("Cleared thread-bound request context: " + request);
  53. }
  55. if (logger.isDebugEnabled()) {
  56. if (failureCause != null) {
  57. this.logger.debug("Could not complete request", failureCause);
  58. }
  59. else {
  60. this.logger.debug("Successfully completed request");
  61. }
  62. }
  63. if (this.publishEvents) {
  64. // Whether or not we succeeded, publish an event.
  65. long processingTime = System.currentTimeMillis() - startTime;
  66. this.webApplicationContext.publishEvent(
  67. new ServletRequestHandledEvent(this,
  68. request.getRequestURI(), request.getRemoteAddr(),
  69. request.getMethod(), getServletConfig().getServletName(),
  70. WebUtils.getSessionId(request), getUsernameForRequest(request),
  71. processingTime, failureCause));
  72. }
  73. }
  74. } 
/**
	 * Process this request, publishing an event regardless of the outcome.
	 * <p>The actual event handling is performed by the abstract
	 * {@link #doService} template method.
	 */
	protected final void processRequest(HttpServletRequest request, HttpServletResponse response)
			throws ServletException, IOException {

		long startTime = System.currentTimeMillis();
		Throwable failureCause = null;

		// Expose current LocaleResolver and request as LocaleContext.
		LocaleContext previousLocaleContext = LocaleContextHolder.getLocaleContext();
		LocaleContextHolder.setLocaleContext(buildLocaleContext(request), this.threadContextInheritable);

		// Expose current RequestAttributes to current thread.
		RequestAttributes previousRequestAttributes = RequestContextHolder.getRequestAttributes();
		ServletRequestAttributes requestAttributes = null;
		if (previousRequestAttributes == null || previousRequestAttributes.getClass().equals(ServletRequestAttributes.class)) {
			requestAttributes = new ServletRequestAttributes(request);
			RequestContextHolder.setRequestAttributes(requestAttributes, this.threadContextInheritable);
		}

		if (logger.isTraceEnabled()) {
			logger.trace("Bound request context to thread: " + request);
		}

		try {
			doService(request, response);
		}
		catch (ServletException ex) {
			failureCause = ex;
			throw ex;
		}
		catch (IOException ex) {
			failureCause = ex;
			throw ex;
		}
		catch (Throwable ex) {
			failureCause = ex;
			throw new NestedServletException("Request processing failed", ex);
		}

		finally {
			// Clear request attributes and reset thread-bound context.
			LocaleContextHolder.setLocaleContext(previousLocaleContext, this.threadContextInheritable);
			if (requestAttributes != null) {
				RequestContextHolder.setRequestAttributes(previousRequestAttributes, this.threadContextInheritable);
				requestAttributes.requestCompleted();
			}
			if (logger.isTraceEnabled()) {
				logger.trace("Cleared thread-bound request context: " + request);
			}

			if (logger.isDebugEnabled()) {
				if (failureCause != null) {
					this.logger.debug("Could not complete request", failureCause);
				}
				else {
					this.logger.debug("Successfully completed request");
				}
			}
			if (this.publishEvents) {
				// Whether or not we succeeded, publish an event.
				long processingTime = System.currentTimeMillis() - startTime;
				this.webApplicationContext.publishEvent(
						new ServletRequestHandledEvent(this,
								request.getRequestURI(), request.getRemoteAddr(),
								request.getMethod(), getServletConfig().getServletName(),
								WebUtils.getSessionId(request), getUsernameForRequest(request),
								processingTime, failureCause));
			}
		}
	}

 

该方法很杂，其他的不要看，就看调用了doService方法即可。此doService由DispatcherServlet重写

 

Java代码 复制代码 收藏代码
  1. @Override
  2. protectedvoid doService(HttpServletRequest request, HttpServletResponse response) throws Exception {
  3. System.out.println("doService");
  4. if (logger.isDebugEnabled()) {
  5. String requestUri = urlPathHelper.getRequestUri(request);
  6. logger.debug("DispatcherServlet with name '" + getServletName() + "' processing " + request.getMethod() +
  7. " request for [" + requestUri + "]");
  8. }
  10. // Keep a snapshot of the request attributes in case of an include,
  11. // to be able to restore the original attributes after the include.
  12. Map<String, Object> attributesSnapshot = null;
  13. if (WebUtils.isIncludeRequest(request)) {
  14. logger.debug("Taking snapshot of request attributes before include");
  15. attributesSnapshot = new HashMap<String, Object>();
  16. Enumeration<?> attrNames = request.getAttributeNames();
  17. while (attrNames.hasMoreElements()) {
  18. String attrName = (String) attrNames.nextElement();
  19. if (this.cleanupAfterInclude || attrName.startsWith("org.springframework.web.servlet")) {
  20. attributesSnapshot.put(attrName, request.getAttribute(attrName));
  21. }
  22. }
  23. }
  25. this.flashMapManager.requestStarted(request);
  27. // Make framework objects available to handlers and view objects.
  28. request.setAttribute(WEB_APPLICATION_CONTEXT_ATTRIBUTE, getWebApplicationContext());
  29. request.setAttribute(LOCALE_RESOLVER_ATTRIBUTE, this.localeResolver);
  30. request.setAttribute(THEME_RESOLVER_ATTRIBUTE, this.themeResolver);
  31. request.setAttribute(THEME_SOURCE_ATTRIBUTE, getThemeSource());
  33. try {
  34. doDispatch(request, response);
  35. }
  36. finally {
  37. this.flashMapManager.requestCompleted(request);
  39. // Restore the original attribute snapshot, in case of an include.
  40. if (attributesSnapshot != null) {
  41. restoreAttributesAfterInclude(request, attributesSnapshot);
  42. }
  43. }
  44. } 
@Override
	protected void doService(HttpServletRequest request, HttpServletResponse response) throws Exception {
System.out.println("doService");
		if (logger.isDebugEnabled()) {
			String requestUri = urlPathHelper.getRequestUri(request);
			logger.debug("DispatcherServlet with name '" + getServletName() + "' processing " + request.getMethod() +
					" request for [" + requestUri + "]");
		}

		// Keep a snapshot of the request attributes in case of an include,
		// to be able to restore the original attributes after the include.
		Map<String, Object> attributesSnapshot = null;
		if (WebUtils.isIncludeRequest(request)) {
			logger.debug("Taking snapshot of request attributes before include");
			attributesSnapshot = new HashMap<String, Object>();
			Enumeration<?> attrNames = request.getAttributeNames();
			while (attrNames.hasMoreElements()) {
				String attrName = (String) attrNames.nextElement();
				if (this.cleanupAfterInclude || attrName.startsWith("org.springframework.web.servlet")) {
					attributesSnapshot.put(attrName, request.getAttribute(attrName));
				}
			}
		}

		this.flashMapManager.requestStarted(request);

		// Make framework objects available to handlers and view objects.
		request.setAttribute(WEB_APPLICATION_CONTEXT_ATTRIBUTE, getWebApplicationContext());
		request.setAttribute(LOCALE_RESOLVER_ATTRIBUTE, this.localeResolver);
		request.setAttribute(THEME_RESOLVER_ATTRIBUTE, this.themeResolver);
		request.setAttribute(THEME_SOURCE_ATTRIBUTE, getThemeSource());

		try {
			doDispatch(request, response);
		}
		finally {
			this.flashMapManager.requestCompleted(request);
			
			// Restore the original attribute snapshot, in case of an include.
			if (attributesSnapshot != null) {
				restoreAttributesAfterInclude(request, attributesSnapshot);
			}
		}
	}

 

其他不要看，就看调用了doDispatch方法

 

Java代码 复制代码 收藏代码
  1. protectedvoid doDispatch(HttpServletRequest request, HttpServletResponse response) throws Exception {
  2. System.out.println("doDispatch");
  3. HttpServletRequest processedRequest = request;
  4. HandlerExecutionChain mappedHandler = null;
  5. int interceptorIndex = -1;
  7. try {
  8. ModelAndView mv;
  9. boolean errorView = false;
  11. try {
  12. processedRequest = checkMultipart(request);
  14. // Determine handler for the current request.
  15. System.out.println("Determine handler for the current request.");
  16. mappedHandler = getHandler(processedRequest, false);
  17. if (mappedHandler == null || mappedHandler.getHandler() == null) {
  18. noHandlerFound(processedRequest, response);
  19. return;
  20. }
  22. // Determine handler adapter for the current request.
  23. System.out.println("Determine handler adapter for the current request.");
  24. HandlerAdapter ha = getHandlerAdapter(mappedHandler.getHandler());
  26. // Process last-modified header, if supported by the handler.
  27. System.out.println("Process last-modified header, if supported by the handler.");
  28. String method = request.getMethod();
  29. boolean isGet = "GET".equals(method);
  30. if (isGet || "HEAD".equals(method)) {
  31. long lastModified = ha.getLastModified(request, mappedHandler.getHandler());
  32. if (logger.isDebugEnabled()) {
  33. String requestUri = urlPathHelper.getRequestUri(request);
  34. logger.debug("Last-Modified value for [" + requestUri + "] is: " + lastModified);
  35. }
  36. if (new ServletWebRequest(request, response).checkNotModified(lastModified) && isGet) {
  37. return;
  38. }
  39. }
  41. // Apply preHandle methods of registered interceptors.
  42. System.out.println("Apply preHandle methods of registered interceptors.");
  43. HandlerInterceptor[] interceptors = mappedHandler.getInterceptors();
  44. if (interceptors != null) {
  45. for (int i = 0; i < interceptors.length; i++) {
  46. HandlerInterceptor interceptor = interceptors[i];
  47. if (!interceptor.preHandle(processedRequest, response, mappedHandler.getHandler())) {
  48. triggerAfterCompletion(mappedHandler, interceptorIndex, processedRequest, response, null);
  49. return;
  50. }
  51. interceptorIndex = i;
  52. }
  53. }
  55. // Actually invoke the handler.
  56. System.out.println("Actually invoke the handler.");
  57. mv = ha.handle(processedRequest, response, mappedHandler.getHandler());
  58. System.out.println("返回mv为空，假设handler已经处理完了");
  60. // Do we need view name translation?
  61. System.out.println("Do we need view name translation?");
  62. if (mv != null && !mv.hasView()) {
  63. mv.setViewName(getDefaultViewName(request));
  64. }
  66. // Apply postHandle methods of registered interceptors.
  67. System.out.println("Apply postHandle methods of registered interceptors.");
  68. if (interceptors != null) {
  69. for (int i = interceptors.length - 1; i >= 0; i--) {
  70. HandlerInterceptor interceptor = interceptors[i];
  71. interceptor.postHandle(processedRequest, response, mappedHandler.getHandler(), mv);
  72. }
  73. }
  74. }
  75. catch (ModelAndViewDefiningException ex) {
  76. logger.debug("ModelAndViewDefiningException encountered", ex);
  77. mv = ex.getModelAndView();
  78. }
  79. catch (Exception ex) {
  80. Object handler = (mappedHandler != null ? mappedHandler.getHandler() : null);
  81. mv = processHandlerException(processedRequest, response, handler, ex);
  82. errorView = (mv != null);
  83. }
  85. // Did the handler return a view to render?
  86. if (mv != null && !mv.wasCleared()) {
  87. System.out.println("执行render了");
  88. render(mv, processedRequest, response);
  89. if (errorView) {
  90. WebUtils.clearErrorRequestAttributes(request);
  91. }
  92. }
  93. else {
  94. if (logger.isDebugEnabled()) {
  95. logger.debug("Null ModelAndView returned to DispatcherServlet with name '" + getServletName() +
  96. "': assuming HandlerAdapter completed request handling");
  97. }
  98. }
  100. // Trigger after-completion for successful outcome.
  101. System.out.println("Trigger after-completion for successful outcome.");
  102. triggerAfterCompletion(mappedHandler, interceptorIndex, processedRequest, response, null);
  103. }
  105. catch (Exception ex) {
  106. // Trigger after-completion for thrown exception.
  107. triggerAfterCompletion(mappedHandler, interceptorIndex, processedRequest, response, ex);
  108. throw ex;
  109. }
  110. catch (Error err) {
  111. ServletException ex = new NestedServletException("Handler processing failed", err);
  112. // Trigger after-completion for thrown exception.
  113. triggerAfterCompletion(mappedHandler, interceptorIndex, processedRequest, response, ex);
  114. throw ex;
  115. }
  117. finally {
  118. // Clean up any resources used by a multipart request.
  119. if (processedRequest != request) {
  120. cleanupMultipart(processedRequest);
  121. }
  122. }
  123. } 
protected void doDispatch(HttpServletRequest request, HttpServletResponse response) throws Exception {
System.out.println("doDispatch");
		HttpServletRequest processedRequest = request;
		HandlerExecutionChain mappedHandler = null;
		int interceptorIndex = -1;

		try {
			ModelAndView mv;
			boolean errorView = false;

			try {
				processedRequest = checkMultipart(request);

				// Determine handler for the current request.
System.out.println("Determine handler for the current request.");				
				mappedHandler = getHandler(processedRequest, false);
				if (mappedHandler == null || mappedHandler.getHandler() == null) {
					noHandlerFound(processedRequest, response);
					return;
				}

				// Determine handler adapter for the current request.
System.out.println("Determine handler adapter for the current request.");
				HandlerAdapter ha = getHandlerAdapter(mappedHandler.getHandler());

                // Process last-modified header, if supported by the handler.
System.out.println("Process last-modified header, if supported by the handler.");
				String method = request.getMethod();
				boolean isGet = "GET".equals(method);
				if (isGet || "HEAD".equals(method)) {
					long lastModified = ha.getLastModified(request, mappedHandler.getHandler());
					if (logger.isDebugEnabled()) {
						String requestUri = urlPathHelper.getRequestUri(request);
						logger.debug("Last-Modified value for [" + requestUri + "] is: " + lastModified);
					}
					if (new ServletWebRequest(request, response).checkNotModified(lastModified) && isGet) {
						return;
					}
				}

				// Apply preHandle methods of registered interceptors.
System.out.println("Apply preHandle methods of registered interceptors.");
				HandlerInterceptor[] interceptors = mappedHandler.getInterceptors();
				if (interceptors != null) {
					for (int i = 0; i < interceptors.length; i++) {
						HandlerInterceptor interceptor = interceptors[i];
						if (!interceptor.preHandle(processedRequest, response, mappedHandler.getHandler())) {
							triggerAfterCompletion(mappedHandler, interceptorIndex, processedRequest, response, null);
							return;
						}
						interceptorIndex = i;
					}
				}

				// Actually invoke the handler.
System.out.println("Actually invoke the handler.");
				mv = ha.handle(processedRequest, response, mappedHandler.getHandler());
System.out.println("返回mv为空，假设handler已经处理完了");

				// Do we need view name translation?
System.out.println("Do we need view name translation?");
				if (mv != null && !mv.hasView()) {
					mv.setViewName(getDefaultViewName(request));
				}

				// Apply postHandle methods of registered interceptors.
System.out.println("Apply postHandle methods of registered interceptors.");
				if (interceptors != null) {
					for (int i = interceptors.length - 1; i >= 0; i--) {
						HandlerInterceptor interceptor = interceptors[i];
						interceptor.postHandle(processedRequest, response, mappedHandler.getHandler(), mv);
					}
				}
			}
			catch (ModelAndViewDefiningException ex) {
				logger.debug("ModelAndViewDefiningException encountered", ex);
				mv = ex.getModelAndView();
			}
			catch (Exception ex) {
				Object handler = (mappedHandler != null ? mappedHandler.getHandler() : null);
				mv = processHandlerException(processedRequest, response, handler, ex);
				errorView = (mv != null);
			}

			// Did the handler return a view to render?
			if (mv != null && !mv.wasCleared()) {
System.out.println("执行render了");
				render(mv, processedRequest, response);
				if (errorView) {
					WebUtils.clearErrorRequestAttributes(request);
				}
			}
			else {
				if (logger.isDebugEnabled()) {
					logger.debug("Null ModelAndView returned to DispatcherServlet with name '" + getServletName() +
							"': assuming HandlerAdapter completed request handling");
				}
			}

			// Trigger after-completion for successful outcome.
System.out.println("Trigger after-completion for successful outcome.");
			triggerAfterCompletion(mappedHandler, interceptorIndex, processedRequest, response, null);
		}

		catch (Exception ex) {
			// Trigger after-completion for thrown exception.
			triggerAfterCompletion(mappedHandler, interceptorIndex, processedRequest, response, ex);
			throw ex;
		}
		catch (Error err) {
			ServletException ex = new NestedServletException("Handler processing failed", err);
			// Trigger after-completion for thrown exception.
			triggerAfterCompletion(mappedHandler, interceptorIndex, processedRequest, response, ex);
			throw ex;
		}

		finally {
			// Clean up any resources used by a multipart request.
			if (processedRequest != request) {
				cleanupMultipart(processedRequest);
			}
		}
	}

 

这里才是最精髓的，代码

 

Java代码 复制代码 收藏代码
  1. System.out.println("Determine handler for the current request."); 
System.out.println("Determine handler for the current request.");

 

对应日志部分

 

Log代码 复制代码 收藏代码
  1. Determine handler for the current request.
  2. TRACE: org.springframework.web.servlet.DispatcherServlet - Testing handler map [org.springframework.web.servlet.handler.BeanNameUrlHandlerMapping@20d1fa4] in DispatcherServlet with name 'appServlet'
  3. TRACE: org.springframework.web.servlet.handler.BeanNameUrlHandlerMapping - No handler mapping found for [/simple]
  4. TRACE: org.springframework.web.servlet.DispatcherServlet - Testing handler map [org.springframework.web.servlet.mvc.annotation.DefaultAnnotationHandlerMapping@5b33a7af] in DispatcherServlet with name 'appServlet'
  5. DEBUG: org.springframework.web.servlet.mvc.annotation.DefaultAnnotationHandlerMapping - Mapping [/simple] to HandlerExecutionChain with handler [org.springframework.samples.mvc.simple.SimpleController@573b7064] and 1 interceptor 
Determine handler for the current request.
TRACE: org.springframework.web.servlet.DispatcherServlet - Testing handler map [org.springframework.web.servlet.handler.BeanNameUrlHandlerMapping@20d1fa4] in DispatcherServlet with name 'appServlet'
TRACE: org.springframework.web.servlet.handler.BeanNameUrlHandlerMapping - No handler mapping found for [/simple]
TRACE: org.springframework.web.servlet.DispatcherServlet - Testing handler map [org.springframework.web.servlet.mvc.annotation.DefaultAnnotationHandlerMapping@5b33a7af] in DispatcherServlet with name 'appServlet'
DEBUG: org.springframework.web.servlet.mvc.annotation.DefaultAnnotationHandlerMapping - Mapping [/simple] to HandlerExecutionChain with handler [org.springframework.samples.mvc.simple.SimpleController@573b7064] and 1 interceptor

 

代码

 

Java代码 复制代码 收藏代码
  1. Determine handler adapter for the current request. 
Determine handler adapter for the current request.

 

对应日志部分

 

Log代码 复制代码 收藏代码
  1. Determine handler adapter for the current request.
  2. TRACE: org.springframework.web.servlet.DispatcherServlet - Testing handler adapter [org.springframework.web.servlet.mvc.HttpRequestHandlerAdapter@557ce3bb]
  3. TRACE: org.springframework.web.servlet.DispatcherServlet - Testing handler adapter [org.springframework.web.servlet.mvc.SimpleControllerHandlerAdapter@6996a298]
  4. TRACE: org.springframework.web.servlet.DispatcherServlet - Testing handler adapter [org.springframework.web.servlet.mvc.annotation.AnnotationMethodHandlerAdapter@783b67a7] 
Determine handler adapter for the current request.
TRACE: org.springframework.web.servlet.DispatcherServlet - Testing handler adapter [org.springframework.web.servlet.mvc.HttpRequestHandlerAdapter@557ce3bb]
TRACE: org.springframework.web.servlet.DispatcherServlet - Testing handler adapter [org.springframework.web.servlet.mvc.SimpleControllerHandlerAdapter@6996a298]
TRACE: org.springframework.web.servlet.DispatcherServlet - Testing handler adapter [org.springframework.web.servlet.mvc.annotation.AnnotationMethodHandlerAdapter@783b67a7]

 

handlerMapping测试了BeanNameUrlHandlerMapping发现没有，接着找DefaultAmmotationHandlerMapping，有对应的映射，搞定。

handlerAdapter测试了HttpRequestHandlerAdapter不行，SimpleControllerHandlerAdapter不行，最后找到AnnotationMethodHandlerAdapter，有对应关系，搞定。

下面来到这段代码

 

Java代码 复制代码 收藏代码
  1. System.out.println("Actually invoke the handler.");
  2. mv = ha.handle(processedRequest, response, mappedHandler.getHandler());
  3. System.out.println("返回mv为空，假设handler已经处理完了"); 
System.out.println("Actually invoke the handler.");
				mv = ha.handle(processedRequest, response, mappedHandler.getHandler());
System.out.println("返回mv为空，假设handler已经处理完了");

 

注意这里的mappedHandler.geteHandler()就是一个AnnotationMethodHandlerAdapter。

再调用

 

Java代码 复制代码 收藏代码
  1. public ModelAndView handle(HttpServletRequest request, HttpServletResponse response, Object handler)
  2. throws Exception {
  3. System.out.println(getClass());
  5. Class<?> clazz = ClassUtils.getUserClass(handler);
  6. Boolean annotatedWithSessionAttributes = this.sessionAnnotatedClassesCache.get(clazz);
  7. if (annotatedWithSessionAttributes == null) {
  8. annotatedWithSessionAttributes = (AnnotationUtils.findAnnotation(clazz, SessionAttributes.class) != null);
  9. this.sessionAnnotatedClassesCache.put(clazz, annotatedWithSessionAttributes);
  10. }
  12. if (annotatedWithSessionAttributes) {
  13. // Always prevent caching in case of session attribute management.
  14. checkAndPrepare(request, response, this.cacheSecondsForSessionAttributeHandlers, true);
  15. // Prepare cached set of session attributes names.
  16. }
  17. else {
  18. // Uses configured default cacheSeconds setting.
  19. checkAndPrepare(request, response, true);
  20. }
  22. // Execute invokeHandlerMethod in synchronized block if required.
  23. if (this.synchronizeOnSession) {
  24. System.out.println("同步");
  25. HttpSession session = request.getSession(false);
  26. if (session != null) {
  27. Object mutex = WebUtils.getSessionMutex(session);
  28. synchronized (mutex) {
  29. return invokeHandlerMethod(request, response, handler);
  30. }
  31. }
  32. }
  34. return invokeHandlerMethod(request, response, handler);
  35. } 
public ModelAndView handle(HttpServletRequest request, HttpServletResponse response, Object handler)
			throws Exception {
System.out.println(getClass());

		Class<?> clazz = ClassUtils.getUserClass(handler);
		Boolean annotatedWithSessionAttributes = this.sessionAnnotatedClassesCache.get(clazz);
		if (annotatedWithSessionAttributes == null) {
			annotatedWithSessionAttributes = (AnnotationUtils.findAnnotation(clazz, SessionAttributes.class) != null);
			this.sessionAnnotatedClassesCache.put(clazz, annotatedWithSessionAttributes);
		}

		if (annotatedWithSessionAttributes) {
			// Always prevent caching in case of session attribute management.
			checkAndPrepare(request, response, this.cacheSecondsForSessionAttributeHandlers, true);
			// Prepare cached set of session attributes names.
		}
		else {
			// Uses configured default cacheSeconds setting.
			checkAndPrepare(request, response, true);
		}

		// Execute invokeHandlerMethod in synchronized block if required.
		if (this.synchronizeOnSession) {
System.out.println("同步");
			HttpSession session = request.getSession(false);
			if (session != null) {
				Object mutex = WebUtils.getSessionMutex(session);
				synchronized (mutex) {
					return invokeHandlerMethod(request, response, handler);
				}
			}
		}

		return invokeHandlerMethod(request, response, handler);
	}

 

其他的无视，看invokeHandlerMethod方法

 

Java代码 复制代码 收藏代码
  1. protected ModelAndView invokeHandlerMethod(HttpServletRequest request, HttpServletResponse response, Object handler)
  2. throws Exception {
  3. System.out.println("invokeHandlerMethod");
  5. ServletHandlerMethodResolver methodResolver = getMethodResolver(handler);
  6. Method handlerMethod = methodResolver.resolveHandlerMethod(request);
  7. ServletHandlerMethodInvoker methodInvoker = new ServletHandlerMethodInvoker(methodResolver);
  8. ServletWebRequest webRequest = new ServletWebRequest(request, response);
  9. ExtendedModelMap implicitModel = new BindingAwareModelMap();
  11. Object result = methodInvoker.invokeHandlerMethod(handlerMethod, handler, webRequest, implicitModel);
  12. System.out.println("result:[" + result + "]");
  13. ModelAndView mav =
  14. methodInvoker.getModelAndView(handlerMethod, handler.getClass(), result, implicitModel, webRequest);
  15. methodInvoker.updateModelAttributes(handler, (mav != null ? mav.getModel() : null), implicitModel, webRequest);
  16. return mav;
  17. } 
protected ModelAndView invokeHandlerMethod(HttpServletRequest request, HttpServletResponse response, Object handler)
			throws Exception {
System.out.println("invokeHandlerMethod");

		ServletHandlerMethodResolver methodResolver = getMethodResolver(handler);
		Method handlerMethod = methodResolver.resolveHandlerMethod(request);
		ServletHandlerMethodInvoker methodInvoker = new ServletHandlerMethodInvoker(methodResolver);
		ServletWebRequest webRequest = new ServletWebRequest(request, response);
		ExtendedModelMap implicitModel = new BindingAwareModelMap();

		Object result = methodInvoker.invokeHandlerMethod(handlerMethod, handler, webRequest, implicitModel);
System.out.println("result:[" + result + "]");
		ModelAndView mav =
				methodInvoker.getModelAndView(handlerMethod, handler.getClass(), result, implicitModel, webRequest);
		methodInvoker.updateModelAttributes(handler, (mav != null ? mav.getModel() : null), implicitModel, webRequest);
		return mav;
	}

 

进入 getModelAndView方法

 

Java代码 复制代码 收藏代码
  1. public ModelAndView getModelAndView(Method handlerMethod, Class handlerType, Object returnValue,
  2. ExtendedModelMap implicitModel, ServletWebRequest webRequest) throws Exception {
  3. System.out.println("getModelAndView[" + returnValue.getClass() + "]");
  5. ResponseStatus responseStatusAnn = AnnotationUtils.findAnnotation(handlerMethod, ResponseStatus.class);
  6. if (responseStatusAnn != null) {
  7. HttpStatus responseStatus = responseStatusAnn.value();
  8. String reason = responseStatusAnn.reason();
  9. if (!StringUtils.hasText(reason)) {
  10. webRequest.getResponse().setStatus(responseStatus.value());
  11. }
  12. else {
  13. webRequest.getResponse().sendError(responseStatus.value(), reason);
  14. }
  16. // to be picked up by the RedirectView
  17. webRequest.getRequest().setAttribute(View.RESPONSE_STATUS_ATTRIBUTE, responseStatus);
  19. responseArgumentUsed = true;
  20. }
  22. // Invoke custom resolvers if present...
  23. if (customModelAndViewResolvers != null) {
  24. System.out.println("Invoke custom resolvers if present...");
  25. for (ModelAndViewResolver mavResolver : customModelAndViewResolvers) {
  26. ModelAndView mav = mavResolver.resolveModelAndView(
  27. handlerMethod, handlerType, returnValue, implicitModel, webRequest);
  28. if (mav != ModelAndViewResolver.UNRESOLVED) {
  29. return mav;
  30. }
  31. }
  32. }
  34. if (returnValue instanceof HttpEntity) {
  35. handleHttpEntityResponse((HttpEntity<?>) returnValue, webRequest);
  36. returnnull;
  37. }
  38. elseif (AnnotationUtils.findAnnotation(handlerMethod, ResponseBody.class) != null) {
  39. System.out.println("原来进入了这个分支");
  40. handleResponseBody(returnValue, webRequest);
  41. returnnull;
  42. }
  43. elseif (returnValue instanceof ModelAndView) {
  44. ModelAndView mav = (ModelAndView) returnValue;
  45. mav.getModelMap().mergeAttributes(implicitModel);
  46. return mav;
  47. }
  48. elseif (returnValue instanceof Model) {
  49. returnnew ModelAndView().addAllObjects(implicitModel).addAllObjects(((Model) returnValue).asMap());
  50. }
  51. elseif (returnValue instanceof View) {
  52. returnnew ModelAndView((View) returnValue).addAllObjects(implicitModel);
  53. }
  54. elseif (AnnotationUtils.findAnnotation(handlerMethod, ModelAttribute.class) != null) {
  55. addReturnValueAsModelAttribute(handlerMethod, handlerType, returnValue, implicitModel);
  56. returnnew ModelAndView().addAllObjects(implicitModel);
  57. }
  58. elseif (returnValue instanceof Map) {
  59. returnnew ModelAndView().addAllObjects(implicitModel).addAllObjects((Map) returnValue);
  60. }
  61. elseif (returnValue instanceof String) {
  62. System.out.println("返回值为String");
  63. returnnew ModelAndView((String) returnValue).addAllObjects(implicitModel);
  64. }
  65. elseif (returnValue == null) {
  66. // Either returned null or was 'void' return.
  67. if (this.responseArgumentUsed || webRequest.isNotModified()) {
  68. returnnull;
  69. }
  70. else {
  71. // Assuming view name translation...
  72. returnnew ModelAndView().addAllObjects(implicitModel);
  73. }
  74. }
  75. elseif (!BeanUtils.isSimpleProperty(returnValue.getClass())) {
  76. // Assume a single model attribute...
  77. addReturnValueAsModelAttribute(handlerMethod, handlerType, returnValue, implicitModel);
  78. returnnew ModelAndView().addAllObjects(implicitModel);
  79. }
  80. else {
  81. thrownew IllegalArgumentException("Invalid handler method return value: " + returnValue);
  82. }
  83. } 
public ModelAndView getModelAndView(Method handlerMethod, Class handlerType, Object returnValue,
				ExtendedModelMap implicitModel, ServletWebRequest webRequest) throws Exception {
System.out.println("getModelAndView[" + returnValue.getClass() + "]");

			ResponseStatus responseStatusAnn = AnnotationUtils.findAnnotation(handlerMethod, ResponseStatus.class);
			if (responseStatusAnn != null) {
				HttpStatus responseStatus = responseStatusAnn.value();
				String reason = responseStatusAnn.reason();
				if (!StringUtils.hasText(reason)) {
					webRequest.getResponse().setStatus(responseStatus.value());
				}
				else {
					webRequest.getResponse().sendError(responseStatus.value(), reason);
				}

				// to be picked up by the RedirectView
				webRequest.getRequest().setAttribute(View.RESPONSE_STATUS_ATTRIBUTE, responseStatus);

				responseArgumentUsed = true;
			}

			// Invoke custom resolvers if present...
			if (customModelAndViewResolvers != null) {
System.out.println("Invoke custom resolvers if present...");
				for (ModelAndViewResolver mavResolver : customModelAndViewResolvers) {
					ModelAndView mav = mavResolver.resolveModelAndView(
							handlerMethod, handlerType, returnValue, implicitModel, webRequest);
					if (mav != ModelAndViewResolver.UNRESOLVED) {
						return mav;
					}
				}
			}

			if (returnValue instanceof HttpEntity) {
				handleHttpEntityResponse((HttpEntity<?>) returnValue, webRequest);
				return null;
			}
			else if (AnnotationUtils.findAnnotation(handlerMethod, ResponseBody.class) != null) {
System.out.println("原来进入了这个分支");
				handleResponseBody(returnValue, webRequest);
				return null;
			}
			else if (returnValue instanceof ModelAndView) {
				ModelAndView mav = (ModelAndView) returnValue;
				mav.getModelMap().mergeAttributes(implicitModel);
				return mav;
			}
			else if (returnValue instanceof Model) {
				return new ModelAndView().addAllObjects(implicitModel).addAllObjects(((Model) returnValue).asMap());
			}
			else if (returnValue instanceof View) {
				return new ModelAndView((View) returnValue).addAllObjects(implicitModel);
			}
			else if (AnnotationUtils.findAnnotation(handlerMethod, ModelAttribute.class) != null) {
				addReturnValueAsModelAttribute(handlerMethod, handlerType, returnValue, implicitModel);
				return new ModelAndView().addAllObjects(implicitModel);
			}
			else if (returnValue instanceof Map) {
				return new ModelAndView().addAllObjects(implicitModel).addAllObjects((Map) returnValue);
			}
			else if (returnValue instanceof String) {
System.out.println("返回值为String");
				return new ModelAndView((String) returnValue).addAllObjects(implicitModel);
			}
			else if (returnValue == null) {
				// Either returned null or was 'void' return.
				if (this.responseArgumentUsed || webRequest.isNotModified()) {
					return null;
				}
				else {
					// Assuming view name translation...
					return new ModelAndView().addAllObjects(implicitModel);
				}
			}
			else if (!BeanUtils.isSimpleProperty(returnValue.getClass())) {
				// Assume a single model attribute...
				addReturnValueAsModelAttribute(handlerMethod, handlerType, returnValue, implicitModel);
				return new ModelAndView().addAllObjects(implicitModel);
			}
			else {
				throw new IllegalArgumentException("Invalid handler method return value: " + returnValue);
			}
		}

 

于是我们看到了熟悉的ResponseBody.class的身影

然后handleResponseBody方法

 

Java代码 复制代码 收藏代码
  1. privatevoid handleResponseBody(Object returnValue, ServletWebRequest webRequest)
  2. throws Exception {
  3. System.out.println("OK搞定");
  4. if (returnValue == null) {
  5. return;
  6. }
  7. HttpInputMessage inputMessage = createHttpInputMessage(webRequest);
  8. HttpOutputMessage outputMessage = createHttpOutputMessage(webRequest);
  9. writeWithMessageConverters(returnValue, inputMessage, outputMessage);
  10. } 
private void handleResponseBody(Object returnValue, ServletWebRequest webRequest)
				throws Exception {
System.out.println("OK搞定");
			if (returnValue == null) {
				return;
			}
			HttpInputMessage inputMessage = createHttpInputMessage(webRequest);
			HttpOutputMessage outputMessage = createHttpOutputMessage(webRequest);
			writeWithMessageConverters(returnValue, inputMessage, outputMessage);
		}

 

可以看到就是在这个方法中直接将字符串发送到浏览器的。writeWithMessageConverters方法无关紧要就不要列出来了。

呼，我是为了完整性，才将方法整个拷贝下来了，其实我们只需要关注主要的一行调用代码即可。

总结一下？

我觉得原理知道即可，关键还是会用，会搭建。下面讲一下如何搭建这个sample。

老办法，从GitHub上将代码clone下来加载到IDE中。

 

Shell代码 复制代码 收藏代码
  1. git clone git://github.com/stephansun/samples.git 
git clone git://github.com/stephansun/samples.git

 

最后补充一下pom.xml

Xml代码 复制代码 收藏代码
  1. <dependencies>
  2. <dependency>
  3. <groupId>org.springframework</groupId>
  4. <artifactId>spring-webmvc</artifactId>
  5. <version>3.1.0.RELEASE</version>
  6. </dependency>
  7. </dependencies>
<dependencies>
  	<dependency>
		<groupId>org.springframework</groupId>
		<artifactId>spring-webmvc</artifactId>
		<version>3.1.0.RELEASE</version>
	</dependency>
  </dependencies>

仅仅加载了spring-webmvc，打开m2e的Dependency Hierarchy栏，观察spring模块间的依赖关系：

spring-webmvc

|- spring-asm

|- spring-beans

|- spring-context

|- spring-context-support

|- spring-core

|- spring-expression

|- spring-web

 

spring-beans

|- spring-core

 

spring-context

|- spring-aop

|- spring-beans

|- spring-core

|- spring-expression

|- spring-asm

 

spring-context-support

|- spring-beans

|- spring-context

|- spring-core

 

spring-core

|- spring-asm

|- commons-logging

 

spring-expression

|- spring-core

 

spring-web

|- aoplliance

|- spring-beans

|- spring-context

|- spring-core

 

Spring发布包

 

  • spring-aop.jar：此JAR文件包含了所有你在应用中使用Spring AOP特性时需要的类。如果应用中使用了其他涉及AOP的Spring功能时，例如声明式事务管理，你也需要将此JAR文件包含进来。
  • spring-beans.jar：此文件包含了所有Spring依赖注入需要的代码。包括bean工厂和相关支持类。大部分情况下，你会需要加入spring-context.jar文件，它包含了建立应用环境上下文需要的代码
  • spring-context.jar：此JAR文件包含了建立Spring应用环境上下文所需的代码，它将主要的ApplicationContext接口和实现、说明、JNDI、调度、主题和验证一起纳入其中
  • spring-context-support.jar：这个包文件包括了Spring的工具代码，其中包括说明、电子邮件、调度支持以及脚本语言支持
  • spring-core.jar：此文件包含了Spring框架的核心代码。它用来处理注解、枚举、任务执行、资源加载以及其他一些即便在Spring框架环境外也会有用的工具和异常类。
  • spring-jdbc.jar：此文件包含了JDBC支持类的代码，例如JdbcTemplate类和JdbcDaoSupport类
  • spring-jms.jar：此文件包含jms的代码
  • spring-orm.jar：此文件包含了对象－关系映射（ORM）工具需要的文件。把这个包加入到classpath上将会给你提供针对Hibernate3，iBatis，JDO，JPA和TopLink的Spring支持
  • spring-test.jar：此文件包含了使用Spring框架编写单元测试和集成测试的支持代码
  • spring-tx.jar：此文件提供了核心的数据访问异常和事务技术支持。这两个概念彼此关系密切，因为一般情况下事务总同某些数据访问代码一起工作的
  • spring-web.jar：此文件包含了Spring Web支持（工具类，绑定器，分段文件解析器）的代码
  • spring-webmvc.jar：此文件包含了Spring MVC的代码
分享到：
| JMS、AMQP实例讲解
评论
发表评论

您还没有登录,请您登录后再发表评论

相关推荐

    基于NSGA2与熵权TOPSIS的电力系统储能选址定容优化及Matpower潮流计算研究

    内容概要：本文详细探讨了利用NSGA2算法进行电力系统中储能系统的选址和定容优化，并结合熵权TOPSIS方法选择最优解。首先介绍了使用Matpower工具包进行潮流计算的基础步骤，随后深入讨论了储能系统引入后的复杂性和优化目标设定。文中展示了如何构建目标函数，包括储能的投资成本和系统电压偏差，并详细解释了NSGA2算法的具体实现，如种群初始化、交叉变异操作以及约束条件处理。最后，通过熵权法确定权重并应用TOPSIS方法对多个优化结果进行评估，选出综合性能最佳的储能配置方案。 适合人群：从事电力系统规划、优化算法研究的专业人士，尤其是对储能系统优化感兴趣的科研人员和技术开发者。 使用场景及目标：适用于需要解决电力系统中储能系统选址和定容问题的实际工程项目。主要目标是在满足系统稳定性要求的前提下，最小化储能系统的投资成本，提高系统的经济性和可靠性。 其他说明：文章提供了详细的代码片段和理论推导，帮助读者更好地理解和实施所提出的优化方法。此外，还提到了一些实际应用中的注意事项，如SOC约束处理、参数选择等，为后续的研究和应用提供了宝贵的实践经验。

    基于python+pyqt5实现视频自动化下载、剪辑和上传系统源码+项目说明.zip

    基于python+pyqt5实现视频自动化下载、剪辑和上传系统源码+项目说明.zip 该项目是用脚本实现部分视频网站视频内容的自动化下载、剪辑以及上传，其中界面是用PyQT做的。 使用的浏览器驱动是undetected_chromedriver，可以跳过tiktok的机器人检查 使用的浏览器是91，版本：Google_Chrome_(64bit)_v91.0.4472.77 【功能】 自动从各种视频网站下载视频 支持视频剪辑和合集制作 支持自动上传视频到视频网站 技术栈 Python PyQT undetected_chromedriver

    西门子S7-1200双套三坐标6轴联动控制系统的设计与实现

    内容概要：本文详细介绍了西门子S7-1200双套三坐标6轴联动控制系统的开发与调试经验。主要内容涵盖双PLC通信机制、轴控制逻辑、安全联锁设计以及触摸屏程序绑定等方面。文中通过具体代码示例展示了如何利用SCL语言实现高效稳定的多轴联动控制，并分享了实际项目中的最佳实践和技术难点解决方案。此外，还讨论了程序结构优化、报警代码设计、数据块管理等关键环节，强调了模块化设计思想的应用及其带来的效率提升。 适合人群：从事工业自动化领域的工程师，尤其是熟悉西门子PLC编程的专业人士。 使用场景及目标：适用于需要进行复杂运动控制的自动化生产线，如汽车制造、电子装配等行业。主要目标是提高生产效率，确保设备运行的安全性和稳定性。 其他说明：文中提到的许多技术和方法不仅限于特定型号的PLC，对于其他品牌的控制器也有一定的借鉴意义。同时，提供的代码片段可以直接应用于类似项目中，帮助开发者快速搭建可靠的控制系统。

    NFC Tools Pro

    NFC Tools是一个应用程序，允许你在你的 NFC 标签和其他 RFID 兼容芯片上读取或写入或编程代码任务。NFC Tools PRO版本包括很多其他的附加功能，比如配置文件管理等。保存你的NFC标签或任务的配置文件，以便你以后重新使用它们。导出和导入很容易。NFC Tools PRO官方版允许你直接从现有的 NFC 标签导入你的记录或任务。 你可以很快编辑你的标签。此外还可以直接运行你的任务配置文件，不需要NFC 标签。

    protobuf-6.30.1-py3-none-any.whl

    该资源为protobuf-6.30.1-py3-none-any.whl，欢迎下载使用哦！

    FLAC3D中壳单元与衬砌单元内力提取及处理技巧

    内容概要：本文详细介绍了如何在FLAC3D中提取壳单元和衬砌单元的关键内力数据，如弯矩、轴力和剪力。针对壳单元，文中提供了具体的FISH命令和函数，展示了如何利用gp.extra属性提取弯矩，并强调了局部坐标系方向的重要性。对于衬砌单元，则介绍了专门的命令和注意事项，如使用liner组件提取轴力和剪力，以及如何处理弯矩数据。此外，还分享了一些实用的经验和技巧，如批量数据处理、单位换算、内力符号规则等。最后，提到了使用Python进行后处理的方法，将提取的数据转化为更直观的形式，便于进一步分析。 适合人群：从事岩土工程、隧道工程及相关领域的工程师和技术人员，尤其是对FLAC3D有一定基础的用户。 使用场景及目标：帮助用户掌握FLAC3D中壳单元和衬砌单元内力提取的具体方法，提高工作效率，确保数据分析的准确性。适用于需要进行结构内力分析、支护设计优化等项目的工程师。 其他说明：文章不仅提供了详细的命令和函数示例，还分享了许多实战经验和常见错误的规避方法，有助于初学者少走弯路。同时，强调了内力符号规则和单位换算的重要性，避免因疏忽导致的重大失误。

    ST PMSM FOC电机控制资料包2.0：全面解析STM32电机控制核心技术与实战技巧

    内容概要：本文详细介绍了ST公司发布的HL07:ST PMSM FOC电机控制资料包2.0的内容及其应用。资料包涵盖了ST芯片电机控制的全源代码、详细文档、多个工程源码、stm32库培训资料及例程源码。文中通过具体的代码示例，如GPIO初始化、PWM配置、ADC采样、Clarke变换、PID调节器、SVPWM生成等，深入剖析了电机控制的关键技术和优化技巧。此外，还揭示了一些隐藏的技术细节和调试技巧，如硬件同步、动态调整PID参数、电机参数自识别等。 适合人群：电机控制工程师、嵌入式开发人员、尤其是对STM32和FOC算法感兴趣的开发者。 使用场景及目标：帮助读者深入了解ST芯片电机控制的具体实现，掌握从硬件配置到算法优化的全过程，提高实际项目的开发效率和质量。适用于需要进行电机控制系统设计、调试和优化的工程项目。 其他说明：资料包中的代码和文档非常实用，提供了丰富的实战经验和优化建议，尤其适合初学者和有一定基础的研发人员。同时，文中提到的一些特殊技巧和注意事项有助于避免常见的开发陷阱，提升系统的稳定性和性能。

    人工智能2025年AI领袖与技术发展趋势：多模态AI、量子计算及行业应用展望

    内容概要：文章探讨了2025年AI技术发展趋势及潜在的GPT级技术突破。首先回顾了GPT系列模型的发展历程及其对自然语言处理领域的深远影响。接着，通过介绍Geoffrey Hinton、李飞飞和张晨等AI领袖的观点，阐述了AI技术在实际应用场景中的挑战与机遇。文中详细描述了AI大模型的演进，包括多模态技术的发展、轻量化趋势以及可控性和可解释性的提升。此外，还介绍了AI计算力的革命性升级，如量子计算、云计算+AI和边缘AI的发展。最后，文章分析了AI在医疗、金融、教育、自动驾驶等行业的落地应用，并指出了面临的挑战与机遇，展望了未来的技术和社会影响。 适合人群：对AI技术感兴趣的从业者、研究人员、企业家及政策制定者。 使用场景及目标：①了解AI技术的最新进展和未来趋势；②探索AI技术在各行业的应用前景；③评估AI技术带来的挑战与机遇，为相关决策提供参考。 阅读建议：本文内容涵盖广泛，既有技术细节又有宏观展望，建议读者结合自身背景选择感兴趣的部分深入阅读，重点关注与自身行业或研究方向相关的章节。

    基于樽海鞘算法优化的极限学习机回归预测及其与BP、GRNN、ELM的性能对比研究

    内容概要：本文详细探讨了基于樽海鞘算法（SSA）优化的极限学习机（ELM）在回归预测任务中的应用，并与传统的BP神经网络、广义回归神经网络（GRNN）以及未优化的ELM进行了性能对比。首先介绍了ELM的基本原理，即通过随机生成输入层与隐藏层之间的连接权重及阈值，仅需计算输出权重即可快速完成训练。接着阐述了SSA的工作机制，利用樽海鞘群体觅食行为优化ELM的输入权重和隐藏层阈值，从而提高模型性能。随后分别给出了BP、GRNN、ELM和SSA-ELM的具体实现代码，并通过波士顿房价数据集和其他工业数据集验证了各模型的表现。结果显示，SSA-ELM在预测精度方面显著优于其他三种方法，尽管其训练时间较长，但在实际应用中仍具有明显优势。 适合人群：对机器学习尤其是回归预测感兴趣的科研人员和技术开发者，特别是那些希望深入了解ELM及其优化方法的人。 使用场景及目标：适用于需要高效、高精度回归预测的应用场景，如金融建模、工业数据分析等。主要目标是提供一种更为有效的回归预测解决方案，尤其是在处理大规模数据集时能够保持较高的预测精度。 其他说明：文中提供了详细的代码示例和性能对比图表，帮助读者更好地理解和复现实验结果。同时提醒使用者注意SSA参数的选择对模型性能的影响，建议进行参数敏感性分析以获得最佳效果。

    工业自动化中汇川PLC与基恩士PLC基于EIP通讯的联机实现及应用

    内容概要：本文详细介绍了汇川PLC与基恩士PLC通过Ethernet/IP (EIP) 协议实现联机的方法及其应用场景。首先，文章解释了硬件配置，包括基恩士KV-7300 CPU搭配KV-EP21v以太网通信模块以及汇川AM-400系列PLC的网口连接。接下来，分别阐述了基恩士和汇川PLC的程序框架，涵盖初始化EIP通讯模块、设置IP地址、建立连接、数据映射及心跳检测机制等关键技术点。此外，文中提供了具体的代码示例和调试建议，如使用Wireshark抓包工具排查问题，并强调了数据同步、字节序转换、超时处理等方面需要注意的地方。最后，分享了一些实践经验，例如确保正确的IP地址分配、合理的缓冲区大小规划、良好的接地措施等。 适合人群：从事工业自动化领域的工程师和技术人员，尤其是对PLC编程有一定基础并希望深入了解不同品牌PLC间通讯机制的专业人士。 使用场景及目标：适用于需要将不同品牌PLC集成到同一个控制系统中的工业项目，旨在提高系统的灵活性和互操作性。通过掌握本文介绍的技术要点，可以有效减少因PLC品牌差异带来的兼容性和稳定性问题。 其他说明：文中不仅提供了理论指导，还结合实际案例进行了深入浅出的讲解，帮助读者更好地理解和应用相关技术。同时，针对可能出现的问题给出了预防和解决方案，使读者能够在实践中少走弯路。

    基于STM32F4的VESC非线性磁链观测器移植与优化

    内容概要：本文详细记录了作者将VESC项目的非线性磁链观测器移植到STM32F4开发板的过程。首先介绍了FOC技术和VESC源码的重要性和特点，然后重点阐述了非线性磁链观测器的实现方法及其核心代码。接着讨论了移植过程中遇到的技术难题，如实时性、稳定性、中断处理、电流采样等问题，并分享了解决这些问题的具体措施。最后展示了测试结果，证明了移植的成功以及观测器的良好性能。 适合人群：具有一定嵌入式开发经验的研发人员，特别是从事电机控制领域的工程师和技术爱好者。 使用场景及目标：适用于希望深入理解VESC源码和非线性磁链观测器的工作机制，掌握STM32F4平台上FOC算法实现的人群。目标是在实际项目中应用这些技术，提高电机控制系统的性能。 其他说明：文中提供了大量实用的代码片段和调试技巧，帮助读者更好地理解和解决问题。此外，作者还分享了一些个人经验和心得，增加了文章的趣味性和实用性。

    Quectel-LTE&5G-Windows-USB-Driver-V2.2.6-beta-20201230

    移远EC20 Windows驱动 操作系统 - 桌面系统 - 移远EC20 Windows驱动

    检证资料jianzhen.ppt

    检证资料jianzhen.ppt

    ### 【嵌入式开发】基于Qt的ATK-DLRK3568实战指南：从入门到项目实战题：嵌

    内容概要：本文档《ATK-DLRK3568嵌入式Qt开发实战V1.2》是正点原子出品的一份面向初学者的嵌入式Qt开发指南，主要内容涵盖嵌入式Linux环境下Qt的安装配置、C++基础、Qt基础、多线程编程、网络编程、多媒体开发、数据库操作以及项目实战案例。文档从最简单的“Hello World”程序开始，逐步引导读者熟悉Qt开发环境的搭建、常用控件的使用、信号与槽机制、UI设计、数据处理等关键技术点。此外，文档还提供了详细的项目实战案例，如车牌识别系统的开发，帮助读者将理论知识应用于实际项目中。 适合人群：具备一定Linux和C++基础，希望快速入门嵌入式Qt开发的初学者或有一定开发经验的研发人员。 使用场景及目标： 1. **环境搭建**：学习如何在Ubuntu环境下搭建Qt开发环境，包括安装必要的工具和库。 2. **基础知识**：掌握C++面向对象编程、Qt基础控件的使用、信号与槽机制等核心概念。 3. **高级功能**：理解多线程编程、网络通信、多媒体处理、数据库操作等高级功能的实现方法。 4. **项目实战**：通过具体的项目案例（如车牌识别系统），巩固

    tcl-tclxml-devel-3.2-26.el8.x64-86.rpm.tar.gz

    1、文件说明： Centos8操作系统tcl-tclxml-devel-3.2-26.el8.rpm以及相关依赖，全打包为一个tar.gz压缩包 2、安装指令： #Step1、解压 tar -zxvf tcl-tclxml-devel-3.2-26.el8.tar.gz #Step2、进入解压后的目录，执行安装 sudo rpm -ivh *.rpm

    C盘清理bat脚本自动清理C盘垃圾文件

    C盘清理bat脚本自动清理C盘垃圾文件

    桶排.txt

    桶排

    基于混沌系统的图像加密算法：循环移位扰乱与水平垂直扩散的应用及性能评估

    内容概要：本文详细介绍了利用混沌系统进行图像加密的方法，重点探讨了Logistic映射生成混沌序列用于图像加密的具体实现。首先，通过生成混沌序列并对其进行预热处理，确保序列的随机性和稳定性。然后，采用循环移位扰乱方法对图像像素进行重新排列，使图像像素位置发生改变。接着，通过水平和垂直扩散步骤进一步打乱像素之间的关联性，增强了加密效果。文中还展示了如何通过直方图、信息熵和相关系数等指标评估加密效果，验证了该方法的有效性。 适合人群：对图像加密技术和混沌系统感兴趣的科研人员、信息安全领域的开发者和技术爱好者。 使用场景及目标：适用于研究和开发高效的图像加密算法，特别是在需要高安全性的应用场景中，如军事通信、隐私保护等领域。目标是提供一种基于混沌系统的高效、安全的图像加密解决方案。 其他说明：文中提供了详细的Python代码实现，帮助读者更好地理解和实践该加密方法。同时，强调了在实际应用中需要注意的一些关键点，如参数选择和优化，以确保最佳的加密效果。

    基于EEMD奇异值熵的滚动轴承故障诊断方法研究

    基于EEMD奇异值熵的滚动轴承故障诊断方法研究

    【数据结构与算法】分块查找算法实现：有序分块数据快速检索方法研究

    内容概要：本文档介绍了分块查找的基本思想及其具体实现方法。分块查找的核心在于将一个数据集划分为若干个块，块内部元素可以无序排列，但块间元素必须保持有序（对于非递减序列，后一块的所有元素均大于前一块）。文档通过C#语言实现了分块查找算法，定义了IndexBlock结构体用于存储每个块的最大值、起始位置和结束位置，并展示了如何初始化分块以及执行具体的查找操作。最后通过一个简单的例子演示了分块查找的应用，当查找成功时返回元素在数组中的索引，否则返回-1表示查找失败。; 适合人群：计算机科学专业学生或有一定编程基础的技术人员。; 使用场景及目标：①理解分块查找算法的工作原理；②掌握利用C#实现分块查找的具体步骤；③学习如何根据实际需求选择合适的查找算法以提高效率。; 其他说明：此文档不仅提供了理论性的概念解释，还结合了实际代码示例帮助读者更好地理解分块查找算法，建议读者在阅读过程中尝试运行代码并理解每一部分的功能。

Magicbox
Global site tag (gtag.js) - Google Analytics