Examples of org.springframework.web.context.support.AbstractRefreshableWebApplicationContext

• org.springframework.web.context.support.AbstractRefreshableWebApplicationContext
  {@link org.springframework.context.support.AbstractRefreshableApplicationContext}subclass which implements the {@link org.springframework.web.context.ConfigurableWebApplicationContext}interface for web environments. Provides a "configLocations" property, to be populated through the ConfigurableWebApplicationContext interface on web application startup.

  This class is as easy to subclass as AbstractRefreshableApplicationContext: All you need to implements is the {@link #loadBeanDefinitions} method;see the superclass javadoc for details. Note that implementations are supposed to load bean definitions from the files specified by the locations returned by the {@link #getConfigLocations} method.

  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 {@link org.springframework.core.io.DefaultResourceLoader}.

  In addition to the special beans detected by {@link org.springframework.context.support.AbstractApplicationContext}, this class detects a bean of type {@link org.springframework.ui.context.ThemeSource}in the context, under the special bean name "themeSource".

  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 {@link org.springframework.web.context.ContextLoader} or as "contextClass"init-param for {@link org.springframework.web.servlet.FrameworkServlet}, replacing the default {@link 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 {@link ConfigurableWebApplicationContext} interface. In contrast, a standaloneapplication context might allow for configuration in custom startup code (for example, {@link org.springframework.context.support.GenericApplicationContext}). @author Juergen Hoeller @since 1.1.3 @see #loadBeanDefinitions @see org.springframework.web.context.ConfigurableWebApplicationContext#setConfigLocations @see org.springframework.ui.context.ThemeSource @see XmlWebApplicationContext

Related Classes of org.springframework.web.context.support.AbstractRefreshableWebApplicationContext