Class BeanValidationPostProcessor
- All Implemented Interfaces:
- BeanPostProcessor,- InitializingBean
BeanPostProcessor that checks JSR-303 constraint annotations
 in Spring-managed beans, throwing an initialization exception in case of
 constraint violations right before calling the bean's init method (if any).- Since:
- 3.0
- Author:
- Juergen Hoeller
- 
Constructor SummaryConstructors
- 
Method SummaryModifier and TypeMethodDescriptionvoidInvoked by the containingBeanFactoryafter it has set all bean properties and satisfiedBeanFactoryAware,ApplicationContextAwareetc.protected voiddoValidate(Object bean) Perform validation of the given bean.postProcessAfterInitialization(Object bean, String beanName) Apply thisBeanPostProcessorto the given new bean instance after any bean initialization callbacks (like InitializingBean'safterPropertiesSetor a custom init-method).postProcessBeforeInitialization(Object bean, String beanName) Apply thisBeanPostProcessorto the given new bean instance before any bean initialization callbacks (like InitializingBean'safterPropertiesSetor a custom init-method).voidsetAfterInitialization(boolean afterInitialization) Choose whether to perform validation after bean initialization (i.e.voidsetValidator(Validator validator) Set the JSR-303 Validator to delegate to for validating beans.voidsetValidatorFactory(ValidatorFactory validatorFactory) Set the JSR-303 ValidatorFactory to delegate to for validating beans, using its default Validator.
- 
Constructor Details- 
BeanValidationPostProcessorpublic BeanValidationPostProcessor()
 
- 
- 
Method Details- 
setValidatorSet the JSR-303 Validator to delegate to for validating beans.Default is the default ValidatorFactory's default Validator. 
- 
setValidatorFactorySet the JSR-303 ValidatorFactory to delegate to for validating beans, using its default Validator.Default is the default ValidatorFactory's default Validator. - See Also:
 
- 
setAfterInitializationpublic void setAfterInitialization(boolean afterInitialization) Choose whether to perform validation after bean initialization (i.e. after init methods) instead of before (which is the default).Default is "false" (before initialization). Switch this to "true" (after initialization) if you would like to give init methods a chance to populate constrained fields before they get validated. 
- 
afterPropertiesSetpublic void afterPropertiesSet()Description copied from interface:InitializingBeanInvoked by the containingBeanFactoryafter it has set all bean properties and satisfiedBeanFactoryAware,ApplicationContextAwareetc.This method allows the bean instance to perform validation of its overall configuration and final initialization when all bean properties have been set. - Specified by:
- afterPropertiesSetin interface- InitializingBean
 
- 
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:
 
- 
doValidatePerform validation of the given bean.- Parameters:
- bean- the bean instance to validate
- See Also:
 
 
-