Performs the actual initialization work for the root application context.
Called by ContextLoaderListener and ContextLoaderServlet.
Looks for a "contextClass" parameter at the web.xml context-param level
to specify the context class type, falling back to the default of
XmlWebApplicationContext if not found. With the default ContextLoader
implementation, any context class specified needs to implement
ConfigurableWebApplicationContext.
Passes a "contextConfigLocation" context-param to the context instance,
parsing it into potentially multiple file paths which can be separated by
any number of commas and spaces, like "applicationContext1.xml,
applicationContext2.xml". If not explicitly specified, the context
implementation is supposed to use a default location (with
XmlWebApplicationContext: "/WEB-INF/applicationContext.xml").
Note: In case of multiple config locations, later bean definitions will
override ones defined in earlier loaded files, at least when using one of
Spring's default ApplicationContext implementations. This can be leveraged
to deliberately override certain bean definitions via an extra XML file.
Above and beyond loading the root application context, this class can
optionally load or obtain and hook up a shared parent context to the root
application context. See the
loadParentContext(ServletContext) method for more information.
Looks for a "contextClass" parameter at the web.xml context-param level to specify the context class type, falling back to the default of XmlWebApplicationContext if not found. With the default ContextLoader implementation, any context class specified needs to implement ConfigurableWebApplicationContext.
Passes a "contextConfigLocation" context-param to the context instance, parsing it into potentially multiple file paths which can be separated by any number of commas and spaces, like "applicationContext1.xml, applicationContext2.xml". If not explicitly specified, the context implementation is supposed to use a default location (with XmlWebApplicationContext: "/WEB-INF/applicationContext.xml").
Note: In case of multiple config locations, later bean definitions will override ones defined in earlier loaded files, at least when using one of Spring's default ApplicationContext implementations. This can be leveraged to deliberately override certain bean definitions via an extra XML file.
Above and beyond loading the root application context, this class can optionally load or obtain and hook up a shared parent context to the root application context. See the loadParentContext(ServletContext) method for more information.