Interprets resource paths as servlet context resources, i.e. as paths beneath
the web application root. Absolute paths, e.g. for files outside the web app root,
can be accessed via "file:" URLs, as implemented by
This is the web context to be subclassed for a different bean definition format.
Such a context implementation can be specified as "contextClass" context-param
for ContextLoader or as "contextClass"
init-param for FrameworkServlet,
replacing the default XmlWebApplicationContext. It will then automatically
receive the "contextConfigLocation" context-param or init-param, respectively.
Note that WebApplicationContext implementations are generally supposed
to configure themselves based on the configuration received through the
ConfigurableWebApplicationContext interface. In contrast, a standalone
application context might allow for configuration in custom startup code
(for example, GenericApplicationContext).
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.
the corresponding Theme, or null if none defined.
Note that, by convention, a ThemeSource should at least be able to
return a default Theme for the default theme name "theme" but may also
return default Themes for other theme names.