Standalone XML application context, taking the context definition files from the class path, interpreting plain paths as class path resource names that include the package path (e.g. "mypackage/myresource.txt"). Useful for test harnesses as well as for application contexts embedded within JARs.
The config location defaults can be overridden via {@link #getConfigLocations}, Config locations can either denote concrete files like "/myfiles/context.xml" or Ant-style patterns like "/myfiles/*-context.xml" (see the {@link org.springframework.util.AntPathMatcher} 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.
This is a simple, one-stop shop convenience ApplicationContext. Consider using the {@link GenericApplicationContext} class in combinationwith an {@link org.springframework.beans.factory.xml.XmlBeanDefinitionReader}for more flexible context setup.
@author Rod Johnson
@author Juergen Hoeller
@see #getResource
@see #getResourceByPath
@see GenericApplicationContext