Class SimpleServletPostProcessor
- All Implemented Interfaces:
- Aware,- BeanPostProcessor,- DestructionAwareBeanPostProcessor,- ServletConfigAware,- ServletContextAware
BeanPostProcessor
 that applies initialization and destruction callbacks to beans that
 implement the Servlet interface.
 After initialization of the bean instance, the Servlet init
 method will be called with a ServletConfig that contains the bean name
 of the Servlet and the ServletContext that it is running in.
 
Before destruction of the bean instance, the Servlet destroy
 will be called.
 
Note that this post-processor does not support Servlet initialization parameters. Bean instances that implement the Servlet interface are supposed to be configured like any other Spring bean, that is, through constructor arguments or bean properties.
For reuse of a Servlet implementation in a plain Servlet container
 and as a bean in a Spring context, consider deriving from Spring's
 HttpServletBean base class that
 applies Servlet initialization parameters as bean properties, supporting
 both the standard Servlet and the Spring bean initialization style.
 
Alternatively, consider wrapping a Servlet with Spring's
 ServletWrappingController.
 This is particularly appropriate for existing Servlet classes,
 allowing to specify Servlet initialization parameters etc.
- Since:
- 1.1.5
- Author:
- Juergen Hoeller
- See Also:
- 
Constructor SummaryConstructors
- 
Method SummaryModifier and TypeMethodDescriptionpostProcessAfterInitialization(Object bean, String beanName) Apply thisBeanPostProcessorto the given new bean instance after any bean initialization callbacks (like InitializingBean'safterPropertiesSetor a custom init-method).voidpostProcessBeforeDestruction(Object bean, String beanName) Apply this BeanPostProcessor to the given bean instance before its destruction, for example, invoking custom destruction callbacks.postProcessBeforeInitialization(Object bean, String beanName) Apply thisBeanPostProcessorto the given new bean instance before any bean initialization callbacks (like InitializingBean'safterPropertiesSetor a custom init-method).booleanrequiresDestruction(Object bean) Determine whether the given bean instance requires destruction by this post-processor.voidsetServletConfig(ServletConfig servletConfig) Set theServletConfigthat this object runs in.voidsetServletContext(ServletContext servletContext) Set theServletContextthat this object runs in.voidsetUseSharedServletConfig(boolean useSharedServletConfig) Set whether to use the shared ServletConfig object passed in throughsetServletConfig, if available.
- 
Constructor Details- 
SimpleServletPostProcessorpublic SimpleServletPostProcessor()
 
- 
- 
Method Details
- 
setServletContextDescription copied from interface:ServletContextAwareSet theServletContextthat this object runs in.Invoked after population of normal bean properties but before an init callback like InitializingBean's afterPropertiesSetor a custom init-method. Invoked after ApplicationContextAware'ssetApplicationContext.- Specified by:
- setServletContextin interface- ServletContextAware
- Parameters:
- servletContext- the ServletContext object to be used by this object
- See Also:
 
- 
setServletConfigDescription copied from interface:ServletConfigAwareSet theServletConfigthat this object runs in.Invoked after population of normal bean properties but before an init callback like InitializingBean's afterPropertiesSetor a custom init-method. Invoked after ApplicationContextAware'ssetApplicationContext.- Specified by:
- setServletConfigin interface- ServletConfigAware
- Parameters:
- servletConfig- the- ServletConfigto be used by this object
- See Also:
 
- 
postProcessBeforeInitializationDescription copied from interface:BeanPostProcessorApply thisBeanPostProcessorto the given new bean instance before any bean initialization callbacks (like InitializingBean'safterPropertiesSetor a custom init-method). The bean will already be populated with property values. The returned bean instance may be a wrapper around the original.The default implementation returns the given beanas-is.- Specified by:
- postProcessBeforeInitializationin interface- BeanPostProcessor
- Parameters:
- bean- the new bean instance
- beanName- the name of the bean
- Returns:
- the bean instance to use, either the original or a wrapped one;
 if null, no subsequent BeanPostProcessors will be invoked
- Throws:
- BeansException- in case of errors
- See Also:
 
- 
postProcessAfterInitializationDescription copied from interface:BeanPostProcessorApply thisBeanPostProcessorto the given new bean instance after any bean initialization callbacks (like InitializingBean'safterPropertiesSetor a custom init-method). The bean will already be populated with property values. The returned bean instance may be a wrapper around the original.In case of a FactoryBean, this callback will be invoked for both the FactoryBean instance and the objects created by the FactoryBean (as of Spring 2.0). The post-processor can decide whether to apply to either the FactoryBean or created objects or both through corresponding bean instanceof FactoryBeanchecks.This callback will also be invoked after a short-circuiting triggered by a InstantiationAwareBeanPostProcessor.postProcessBeforeInstantiation(java.lang.Class<?>, java.lang.String)method, in contrast to all otherBeanPostProcessorcallbacks.The default implementation returns the given beanas-is.- Specified by:
- postProcessAfterInitializationin interface- BeanPostProcessor
- Parameters:
- bean- the new bean instance
- beanName- the name of the bean
- Returns:
- the bean instance to use, either the original or a wrapped one;
 if null, no subsequent BeanPostProcessors will be invoked
- Throws:
- BeansException- in case of errors
- See Also:
 
- 
postProcessBeforeDestructionDescription copied from interface:DestructionAwareBeanPostProcessorApply this BeanPostProcessor to the given bean instance before its destruction, for example, invoking custom destruction callbacks.Like DisposableBean's destroyand a custom destroy method, this callback will only apply to beans which the container fully manages the lifecycle for. This is usually the case for singletons and scoped beans.- Specified by:
- postProcessBeforeDestructionin interface- DestructionAwareBeanPostProcessor
- Parameters:
- bean- the bean instance to be destroyed
- beanName- the name of the bean
- Throws:
- BeansException- in case of errors
- See Also:
 
- 
requiresDestructionDescription copied from interface:DestructionAwareBeanPostProcessorDetermine whether the given bean instance requires destruction by this post-processor.The default implementation returns true. If a pre-5 implementation ofDestructionAwareBeanPostProcessordoes not provide a concrete implementation of this method, Spring silently assumestrueas well.- Specified by:
- requiresDestructionin interface- DestructionAwareBeanPostProcessor
- Parameters:
- bean- the bean instance to check
- Returns:
- trueif- DestructionAwareBeanPostProcessor.postProcessBeforeDestruction(java.lang.Object, java.lang.String)is supposed to be called for this bean instance eventually, or- falseif not needed