SpringMVC的初始化

初始化

透过现象看本质,DispatcherServlet我们在配置文件中配置,光看其名字就知道这是一个Servlet,而Servlet我们比较熟悉,声明周期无非就是init–>service–>destroy。而DispatcherServlet本身没有该方法,就想到方法应该在其父类。
在此之前,应该先研究下关键几个类的关系。
最终是调用HttpServletBean的init()方法

Spring中的类实在是太多了,我个人在最初学习的时候毫无头绪,过目就忘,而且看完Spring再去看Mybatis,感觉Mybatis超简单,原因就是Mybatis类比较少。针对于类多的情况,我主张是去先看接口,因为接口定义了一种规范,带着这种规范去看某个类,目的就明确一些。

public final void init() throws ServletException {

		// Set bean properties from init parameters.
		PropertyValues pvs = new ServletConfigPropertyValues(getServletConfig(), this.requiredProperties);
		if (!pvs.isEmpty()) {
			try {
				BeanWrapper bw = PropertyAccessorFactory.forBeanPropertyAccess(this);
				ResourceLoader resourceLoader = new ServletContextResourceLoader(getServletContext());
				bw.registerCustomEditor(Resource.class, new ResourceEditor(resourceLoader, getEnvironment()));
				initBeanWrapper(bw);
				bw.setPropertyValues(pvs, true);
			}
			catch (BeansException ex) {
				if (logger.isErrorEnabled()) {
					logger.error("Failed to set bean properties on servlet '" + getServletName() + "'", ex);
				}
				throw ex;
			}
		}

		// Let subclasses do whatever initialization they like.
		initServletBean();
	}	

HttpServletBean是一个抽象类,其中的initServletBean()又去调用子类FrameworkServlet的

protected final void initServletBean() throws ServletException {
		getServletContext().log("Initializing Spring " + getClass().getSimpleName() + " '" + getServletName() + "'");
		if (logger.isInfoEnabled()) {
			logger.info("Initializing Servlet '" + getServletName() + "'");
		}
		long startTime = System.currentTimeMillis();

		try {
			this.webApplicationContext = initWebApplicationContext();
			initFrameworkServlet();
		}
		catch (ServletException | RuntimeException ex) {
			logger.error("Context initialization failed", ex);
			throw ex;
		}

		if (logger.isDebugEnabled()) {
			String value = this.enableLoggingRequestDetails ?
					"shown which may lead to unsafe logging of potentially sensitive data" :
					"masked to prevent unsafe logging of potentially sensitive data";
			logger.debug("enableLoggingRequestDetails='" + this.enableLoggingRequestDetails +
					"': request parameters and headers will be " + value);
		}

其中initWebApplicationContext方法是关键

protected WebApplicationContext initWebApplicationContext() {
   	WebApplicationContext rootContext =
   			WebApplicationContextUtils.getWebApplicationContext(getServletContext());
   	WebApplicationContext wac = null;

   	if (this.webApplicationContext != null) {
   		// 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);
   			}
   		}
   	}
   	if (wac == null) {
   		// 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();
   	}
   	if (wac == null) {
   		// No context instance is defined for this servlet -> create a local one
   		wac = createWebApplicationContext(rootContext);
   	}

   	if (!this.refreshEventReceived) {
   		// 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.
   		synchronized (this.onRefreshMonitor) {
   			onRefresh(wac);
   		}
   	}

   	if (this.publishContext) {
   		// Publish the context as a servlet context attribute.
   		String attrName = getServletContextAttributeName();
   		getServletContext().setAttribute(attrName, wac);
   	}

   	return wac;
   }

在创建完webApplicationContext之后onFresh()方法,也就是刷新容器上下文,回到了DispatcherServlet中,初始化了我们SpringMVC中的9大组件

	protected void initStrategies(ApplicationContext context) {
   		initMultipartResolver(context);
   		initLocaleResolver(context);
   		initThemeResolver(context);
   		initHandlerMappings(context);
   		initHandlerAdapters(context);
   		initHandlerExceptionResolvers(context);
   		initRequestToViewNameTranslator(context);
   		initViewResolvers(context);
   		initFlashMapManager(context);
   }

其中initHandlerMappings()是初始化controller方法和url关系映射,关于这一步就要看HandlerMapping的实现类AbstractDetectingUrlHandlerMapping

public void initApplicationContext() throws ApplicationContextException {
   	super.initApplicationContext();
   	detectHandlers();
   }

protected void detectHandlers() throws BeansException {
   	ApplicationContext applicationContext = obtainApplicationContext();
   	String[] beanNames = (this.detectHandlersInAncestorContexts ?
   			BeanFactoryUtils.beanNamesForTypeIncludingAncestors(applicationContext, Object.class) :
   			applicationContext.getBeanNamesForType(Object.class));

   	// Take any bean name that we can determine URLs for.
   	for (String beanName : beanNames) {
   		String[] urls = determineUrlsForHandler(beanName);
   		if (!ObjectUtils.isEmpty(urls)) {
   			// URL paths found: Let's consider it a handler.
   			registerHandler(urls, beanName);
   		}
   	}

   	if ((logger.isDebugEnabled() && !getHandlerMap().isEmpty()) || logger.isTraceEnabled()) {
   		logger.debug("Detected " + getHandlerMap().size() + " mappings in " + formatMappingName());
   	}
   }

determineUrlsForHandler()在获取url之后,registerHandler()对handler进行注册。

  • 1
    点赞
  • 0
    收藏
    觉得还不错? 一键收藏
  • 0
    评论
评论
添加红包

请填写红包祝福语或标题

红包个数最小为10个

红包金额最低5元

当前余额3.43前往充值 >
需支付:10.00
成就一亿技术人!
领取后你会自动成为博主和红包主的粉丝 规则
hope_wisdom
发出的红包
实付
使用余额支付
点击重新获取
扫码支付
钱包余额 0

抵扣说明:

1.余额是钱包充值的虚拟货币,按照1:1的比例进行支付金额的抵扣。
2.余额无法直接购买下载,可以购买VIP、付费专栏及课程。

余额充值