{@link org.springframework.web.context.WebApplicationContext} implementationwhich takes its configuration from XML documents, understood by an {@link org.springframework.beans.factory.xml.XmlBeanDefinitionReader}. This is essentially the equivalent of {@link org.springframework.context.support.AbstractXmlApplicationContext}for a web environment.
By default, the configuration will be taken from "/WEB-INF/applicationContext.xml" for the root context, and "/WEB-INF/test-servlet.xml" for a context with the namespace "test-servlet" (like for a DispatcherServlet instance with the servlet-name "test").
The config location defaults can be overridden via the "contextConfigLocation" context-param of {@link org.springframework.web.context.ContextLoader} and servletinit-param of {@link org.springframework.web.servlet.FrameworkServlet}. Config locations can either denote concrete files like "/WEB-INF/context.xml" or Ant-style patterns like "/WEB-INF/*-context.xml" (see {@link org.springframework.util.PathMatcher}javadoc for pattern details).
Note: In case of multiple config locations, later bean definitions will override ones defined in earlier loaded files. This can be leveraged to deliberately override certain bean definitions via an extra XML file.
For a WebApplicationContext that reads in a different bean definition format, create an analogous subclass of {@link AbstractRefreshableWebApplicationContext}. Such a context implementation can be specified as "contextClass" context-param for ContextLoader or "contextClass" init-param for FrameworkServlet.
@author Rod Johnson
@author Juergen Hoeller
@see #setNamespace
@see #setConfigLocations
@see org.springframework.beans.factory.xml.XmlBeanDefinitionReader
@see org.springframework.web.context.ContextLoader#initWebApplicationContext
@see org.springframework.web.servlet.FrameworkServlet#initWebApplicationContext