Docjar: A Java Source and Docuemnt Enginecom.*    java.*    javax.*    org.*    all    new    plug-in

Quick Search    Search Deep

org.springframework.web.context.support.* (15)

org.springframework.web.context: Javadoc index of package org.springframework.web.context.


Package Samples:

org.springframework.web.context.support: Contains the application context subinterface for web applications, and the ContextLoaderListener that bootstraps the root web application context.  

Classes:

AbstractRefreshableWebApplicationContext: AbstractRefreshableApplicationContext subclass that implements the ConfigurableWebApplicationContext interface for web environments. Pre-implements a "configLocation" 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 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 getConfigLocations method. ...
ContextLoader: Performs the actual initialization work for the root application context. Called by ContextLoaderListener and ContextLoaderServlet. Looks for a "contextClass" parameter at the web.xml context-param level to specify the context class type, falling back to the default of org.springframework.web.context.support.XmlWebApplicationContext if not found. With the default ContextLoader implementation, any context class specified needs to implement ConfigurableWebApplicationContext. Passes a "contextConfigLocation" context-param to the context instance, parsing it into potentially multiple file paths which ...
ContextLoaderServlet: Bootstrap servlet to start up Spring's root WebApplicationContext. Simply delegates to ContextLoader. This servlet should have a lower load-on-startup value in web.xml than any servlets that access the root web application context. Note that this class has been deprecated for containers implementing Servlet API 2.4 or higher, in favor of ContextLoaderListener. According to Servlet 2.4, listeners must be initialized before load-on-startup servlets. Many Servlet 2.3 containers already enforce this behavior. If you use such a container, this servlet can be replaced with ContextLoaderListener. Else ...
XmlWebApplicationContext: WebApplicationContext implementation that takes configuration from an XML document, understood by an XmlBeanDefinitionReader. This is essentially the equivalent of AbstractXmlApplicationContext and its subclasses for a web environment. By default, the configuration will be taken from "/WEB-INF/applicationContext.xml" for the root context, and "/WEB-INF/test-servlet.xml" for a context with the namespace "test-servlet" (like for a DispatcherServlet instance with the servlet-name "test"). The config location defaults can be overridden via the "contextConfigLocation" context param of ContextLoader ...
ServletContextPropertyPlaceholderConfigurer: Subclass of PropertyPlaceholderConfigurer that resolves placeholders as ServletContext init parameters (that is, web.xml context-param entries). Can be combined with "locations" and/or "properties" values in addition to web.xml context-params. Alternatively, can be defined without local properties, to resolve all placeholders as web.xml context-params (or JVM system properties). If a placeholder could not be resolved against the provided local properties within the application, this configurer will fall back to ServletContext parameters. Can also be configured to let ServletContext init parameters ...
WebApplicationContext: Interface to provide configuration for a web application. This is read-only while the application is running, but may be reloaded if the implementation supports this. This interface adds a getServletContext method to the generic ApplicationContext interface, and defines a well-known application attribute name that the root context must be bound to in the bootstrap process. Like generic application contexts, web application contexts are hierarchical. There is a single root context per application, while each servlet in the application (including a dispatcher servlet in the MVC framework) has its ...
ServletContextAttributeExporter: Exporter that takes Spring-defined objects and exposes them as ServletContext attributes. Usually, bean references will be used to export Spring-defined beans as ServletContext attributes. Useful to make Spring-defined beans available to code that is not aware of Spring at all, but rather just of the Servlet API. Client code can then use plain ServletContext attribute lookups to access those objects, despite them being defined in a Spring application context. Alternatively, consider using the WebApplicationContextUtils class to access Spring-defined beans via the WebApplicationContext interface. ...
ServletContextFactoryBean: Simple FactoryBean that exposes the ServletContext for bean references. Can be used as alternative to implementing ServletContextAware, allowing to pass in the ServletContext to a constructor argument or any custom bean property. Note that there's a special FactoryBean for exposing a specific ServletContext attribute, named ServletContextAttributeFactoryBean. So if all you need from the ServletContext is access to a specific attribute, ServletContextAttributeFactoryBean allows you to expose a constructor argument or bean property of the attribute type, which is a preferable to a dependency on the ...
ServletContextResourcePatternResolver: ServletContext-aware subclass of PathMatchingResourcePatternResolver, able to find matching resources below the web application root directory via Servlet 2.3's ServletContext.getResourcePaths . Falls back to the superclass' file system checking for other resources. The advantage of using ServletContext.getResourcePaths to find matching files is that it will work in a WAR file which has not been expanded too. For Servlet containers that do not support Servlet 2.3 or above, this resolver will always fall back to file system checking, which requires an expanded WAR file.
ServletContextAttributeFactoryBean: FactoryBean that fetches a specific, existing ServletContext attribute. Exposes that ServletContext attribute when used as bean reference, effectively making it available as named Spring bean instance. Intended to link in ServletContext attributes that exist before the startup of the Spring application context. Typically, such attributes will have been put there by third-party web frameworks. In a purely Spring-based web application, no such linking in of ServletContext attrutes will be necessary.
WebApplicationContextUtils: Convenience methods to retrieve the root WebApplicationContext for a given ServletContext. This is e.g. useful for accessing a Spring context from within custom web views or Struts actions. Note that there are more convenient ways of accessing the root context for many web frameworks, either part of Spring or available as external library. This helper class is just the most generic way to access the root context.
ContextLoaderListener: Bootstrap listener to start up Spring's root WebApplicationContext. Simply delegates to ContextLoader. This listener should be registered after Log4jConfigListener in web.xml, if the latter is used. For Servlet 2.2 containers and Servlet 2.3 ones that do not initalize listeners before servlets, use ContextLoaderServlet. See the latter's Javadoc for details.
ServletContextAwareProcessor: BeanPostProcessor implementation that passes the ServletContext to beans that implement the ApplicationContextAware or ResourceLoaderAware interfaces. If both are implemented, the latter is satisfied first. Web application contexts will automatically register this with their underlying bean factory. Applications do not use this directly.
ConfigurableWebApplicationContext: Interface to be implemented by configurable web application contexts. Expected by ContextLoader and FrameworkServlet. Note: The setters of this interface need to be called before an invocation of the refresh method inherited from ConfigurableApplicationContext. They do not cause an initialization of the context on their own.
ServletContextAware: Interface to be implemented by any object that wishes to be notified of the ServletContext (typically determined by the WebApplicationContext) that it runs in. Can be implemented instead of ApplicationContextAware (casting the context to WebApplicationContext) if all an object needs is a reference to the ServletContext.
ServletContextResource: Resource implementation for ServletContext resources, interpreting relative paths within the web application root. Always supports stream access, but only allows java.io.File access when the web application archive is expanded. Always supports resolution as URL.
StaticWebApplicationContext: Static WebApplicationContext implementation for testing. Not for use in production applications. In addition to the special beans detected by AbstractApplicationContext, this class detects a ThemeSource bean in the context, with the name "themeSource".
RequestHandledEvent: Event raised when a request is handled within a WebApplicationContext. Supported by Spring's own FrameworkServlet, but can also be raised by any other web component.
WebApplicationObjectSupport: Convenient superclass for application objects running in a WebApplicationContext. Provides getWebApplicationContext, getServletContext, and getTempDir methods.
ServletContextResourceLoader: ResourceLoader implementation that resolves paths as ServletContext resources, for use outside a WebApplicationContext.
PerformanceMonitorListener: Listener that logs the response times of web requests. To be registered in a WebApplicationContext.

Home | Contact Us | Privacy Policy | Terms of Service