Standalone XML application context, taking the context definition files
from the file system or from URLs, interpreting plain paths as relative
file system locations (e.g. "mydir/myfile.txt"). Useful for test harnesses
as well as for standalone environments.

NOTE: Plain paths will always be interpreted as relative
to the current VM working directory, even if they start with a slash.
(This is consistent with the semantics in a Servlet container.)
Use an explicit "file:" prefix to enforce an absolute file path.

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 the
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.

getConfigLocations

Return an array of resource locations, referring to the XML bean definition
files that this context should be built with. Can also include location
patterns, which will get resolved via a ResourcePatternResolver.

The default implementation returns null. Subclasses can override
this to provide a set of resource locations to load bean definitions from.