Standalone XML application context, taking the context definition files
from the file system or from URLs. Mainly useful for test harnesses,
but also for standalone environments.
Treats resource paths as file system resources, when using
getResource. Resource paths are considered relative
to the current VM working directory, even if they start with a slash.
The config location defaults can be overridden via getConfigLocations,
Config locations can either denote concrete files like "/myfiles/context.xml"
or Ant-style patterns like "/myfiles/*-context.xml" (see 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.
This is a simple, one-stop shop convenience ApplicationContext.
Consider using the GenericApplicationContext class in combination
with an XmlBeanDefinitionReader for more flexible context setup.
Treats resource paths as file system resources, when using
getResource. Resource paths are considered relative to the current VM working directory, even if they start with a slash.The config location defaults can be overridden via
getConfigLocations, Config locations can either denote concrete files like "/myfiles/context.xml" or Ant-style patterns like "/myfiles/*-context.xml" (see 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.
This is a simple, one-stop shop convenience ApplicationContext. Consider using the GenericApplicationContext class in combination with an XmlBeanDefinitionReader for more flexible context setup.