In the post Executing code on the creation or destruction of a bean in Spring I explain three ways to execute code on the creation or destruction of a Bean in Spring.
With two of these ways you can set the execution of a specific custom method:
- with the annotations @PostConstruct and @PreDestroy
- configuring the properties init-method and destroy-method
There is a very convenient way in the case that more beans have methods with the same name to be executed on their creation and destruction, i.e. you can specify a default method for all the beans.
Continue reading “How to set a default method to running code on the creation or destruction of a bean”
PropertyEditor is an interface that provides a support for the conversion of the value of a property (usually of type String) in an object that can be Date, URL, etc. Continue reading “PropertyEditors in Spring 3”
There are 3 ways to execute code to create a bean in Spring:
- with the annotation @PostConstruct
- implementing the interface InitializingBean
- configuring the property init-method
The reason why you run code when you create a bean is often to check the dependencies, and assign a default value, or automated actions such as starting a scheduled task.
The constructor of the bean may not be suitable for this purpose because the bean is not fully initialized until the constructor has not completed. Continue reading “Executing code on the creation or destruction of a bean in Spring”