Using Grails, we often set some application wide constants or config properties or execute certain tasks in bootstrap.groovy\u00a0when the application starts .\u00a0A better approach is to create a new class in src\/groovy and have it implement Initialization bean\u00a0interface<\/p>\n
[java]
\nimport org.springframework.beans.factory.InitializingBean
\nclass MyClass implements InitializingBean {
\nvoid afterPropertiesSet() {
\n \/\/ do you stuff here.
\n }
\n}
\n[\/java]<\/p>\n
Now in resources.groovy, add<\/p>\n
[java]
\nmyClass(MyClass) { bean ->
\n bean.autowire = ‘byName’
\n}
\n[\/java]<\/p>\n
This would make it a spring managed bean and will be executed at the time the spring beans are initialized.
\nThis is a no mess way of doing a task, while the application is coming up.<\/p>\n
Thanks<\/p>\n
Sachin Anand<\/p>\n
sachin@intelligrape.com<\/span><\/p>\n @babasachinanand<\/span><\/p>\n","protected":false},"excerpt":{"rendered":" Using Grails, we often set some application wide constants or config properties or execute certain tasks in bootstrap.groovy\u00a0when the application starts .\u00a0A better approach is to create a new class in src\/groovy and have it implement Initialization bean\u00a0interface [java] import org.springframework.beans.factory.InitializingBean class MyClass implements InitializingBean { void afterPropertiesSet() { \/\/ do you stuff here. } […]<\/p>\n","protected":false},"author":14,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"iawp_total_views":3,"footnotes":""},"categories":[7],"tags":[178,862,864,863],"class_list":["post-6178","post","type-post","status-publish","format-standard","hentry","category-grails","tag-bootstrap","tag-initialization","tag-initialization-bean","tag-spring-bean"],"aioseo_notices":[],"aioseo_head":"\n\t\t\n\t\n\t\n\t\n\t\n\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t