![\"null\"](\"http:\/\/codethataint.com\/blog\/wp-content\/uploads\/2019\/05\/1.jpeg\")
<\/p>\n
InitializingBean and DisposableBean callback interfaces<\/strong> Refer Here<\/a> and here<\/a><\/p>\n Custom init() and destroy() methods in bean configuration file<\/strong> @PostConstruct and @PreDestroy annotations<\/strong> The @PostConstruct annotation is used on a method that needs to be executed after dependency injection is done to perform any initialization.<\/p>\n The @PreDestroy annotation is used on methods as a callback notification to signal that the instance is in the process of being removed by the container.<\/p>\n @PostConstruct vs init-method vs afterPropertiesSet<\/strong> Spring.xml<\/strong><\/p>\n Output<\/strong><\/p>\n When to use what?<\/strong> Spring Bean life Cycle is hooked to the below 4 interfaces Methods InitializingBean and DisposableBean callback interfaces *Aware interfaces for specific behavior Custom init() and destroy() methods in bean configuration file @PostConstruct and @PreDestroy annotations InitializingBean and DisposableBean callback interfaces InitializingBean and DisposableBean are two marker interfaces, a useful way for Spring to perform certain… Continue reading
\nInitializingBean and DisposableBean are two marker interfaces, a useful way for Spring to perform certain actions upon bean initialization and destruction.<\/p>\n\n
\nUsing init-method and destroy-method as attribute in bean configuration file for bean to perform certain actions upon initialization and destruction. <\/p>\n
\nWe can manage lifecycle of a bean by using method-level annotations @PostConstruct and @PreDestroy.<\/p>\n
\nThere is any difference but there are priorities in the way they work. @PostConstruct, init-method.@PostConstruct is a JSR-250 annotation while init-method is Spring’s way of having an initializing method.If you have a @PostConstruct method, this will be called first before the initializing methods are called. If your bean implements InitializingBean and overrides afterPropertiesSet, first @PostConstruct is called, then the afterPropertiesSet and then init-method.<\/p>\n\r\n@Component\r\npublic class MyComponent implements InitializingBean {\r\n\t\r\n\t@Value("${mycomponent.value:Magic}")\r\n\tpublic String value;\r\n\t\r\n\tpublic MyComponent() {\r\n\t\tlog.info("MyComponent in constructor: [{}]", value); \/\/ (0) displays: Null [properties not set yet]\r\n\t}\r\n\t\r\n\t@PostConstruct\r\n\tpublic void postConstruct() {\r\n\t\tlog.info("MyComponent in postConstruct: [{}]", value); \/\/ (1) displays: Magic\r\n\t}\r\n\r\n\t@Override \/\/ (equivalent to init-method in XML; overrides InitializingBean.afterPropertiesSet()\r\n\tpublic void afterPropertiesSet() {\r\n\t\tlog.info("MyComponent in afterPropertiesSet: [{}]", value); \/\/ (2) displays: Magic\r\n\t}\t\r\n\r\n public void initIt() throws Exception {\r\n\t log.info("MyComponent in init: " + value);\r\n\t}\r\n\r\n\t@PreDestroy\r\n\tpublic void preDestroy() {\r\n\t\tlog.info("MyComponent in preDestroy: [{}], self=[{}]", value); \/\/ (3) displays: \r\n\t}\r\n\r\n public void cleanUp() throws Exception {\r\n\t log.info("Spring Container is destroy! Customer clean up");\r\n\t}\r\n}\r\n<\/pre>\n\r\n<beans xmlns="http:\/\/www.springframework.org\/schema\/beans"\r\n\txmlns:xsi="http:\/\/www.w3.org\/2001\/XMLSchema-instance"\r\n\txsi:schemaLocation="http:\/\/www.springframework.org\/schema\/beans\r\n\thttp:\/\/www.springframework.org\/schema\/beans\/spring-beans-2.5.xsd">\r\n\t<bean id="customerService" class="com.mkyong.customer.services.CustomerService" \r\n\t\tinit-method="initIt" destroy-method="cleanUp"> \t\t\r\n\t\t<property name="message" value="i'm property message" \/>\r\n\t<\/bean>\t\t\r\n<\/beans>\r\n<\/pre>\n
\r\nMyComponent in constructor: [null]\r\nMyComponent in postConstruct: [Magic]\r\nMyComponent in init: [Magic from XML]\r\nMyComponent in afterPropertiesSet: [Magic]\r\nMyComponent in preDestroy: [Magic]\r\nSpring Container is destroy! Customer clean up\r\n<\/pre>\n
\ninit-method and destroy-method<\/em><\/strong> is the recommended approach because of no direct dependency to Spring Framework and we can create our own methods.
\nInitializingBean and DisposableBean<\/em><\/strong> To interact with the container’s management of the bean lifecycle, you can implement the Spring InitializingBean and DisposableBean interfaces. The container calls afterPropertiesSet() for the former and destroy() for the latter to allow the bean to perform certain actions upon initialization and destruction of your beans.
\n@PostConstruct and @PreDestroy<\/em><\/strong> – The JSR-250 @PostConstruct and @PreDestroy annotations are generally considered best practice for receiving lifecycle callbacks in a modern Spring application. Using these annotations means that your beans are not coupled to Spring specific interfaces.<\/p>\n","protected":false},"excerpt":{"rendered":"