Portlet-based {@link org.springframework.web.context.WebApplicationContext}implementation which 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 portlet environment.
By default, the configuration will be taken from "/WEB-INF/applicationContext.xml" for the root context, and "/WEB-INF/test-portlet.xml" for a context with the namespace "test-portlet" (like for a DispatcherPortlet instance with the portlet-name "test").
The config location defaults can be overridden via the "contextConfigLocation" portlet init-param of {@link org.springframework.web.portlet.FrameworkPortlet}. 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 Portlet-based context that reads in a different bean definition format, create an analogous subclass of {@link AbstractRefreshablePortletApplicationContext}. Such a context implementation can be specified as "contextClass" init-param for a FrameworkPortlet instance.
@author Juergen Hoeller
@author John A. Lewis
@since 2.0
@see #setNamespace
@see #setConfigLocations
@see org.springframework.beans.factory.xml.XmlBeanDefinitionReader
@see org.springframework.web.portlet.FrameworkPortlet#initPortletApplicationContext