{"id":549,"date":"2010-04-15T14:55:03","date_gmt":"2010-04-15T09:25:03","guid":{"rendered":"https:\/\/2thenew.online\/blog\/?p=549"},"modified":"2010-06-09T15:31:32","modified_gmt":"2010-06-09T10:01:32","slug":"reloading-a-gsp-in-test-production-environment","status":"publish","type":"post","link":"https:\/\/2thenew.online\/blog\/reloading-a-gsp-in-test-production-environment\/","title":{"rendered":"Reloading a GSP in test & production environment."},"content":{"rendered":"

In one of my project I need to generate GSP (groovy server pages) on the fly and write them on the file system. There was a quartz job that updates the GSP page on regular intervals. <\/p>\n

The problem was, this functionality worked flawless in the development environment but fails in test and production environment. In test and production environment you can force and reload the GSP in order to see the latest one.<\/p>\n

You can force the GSP to reload by writing this following code in your Config.groovy file:
\n<\/p>\n

\r\ngrails.gsp.reload.enable = true\r\n<\/pre>\n
<\/block><\/p>\n
Any suggestions and comments are welcome.<\/p>\n
Cheers
\n~Chandan Luthra~<\/p>\n","protected":false},"excerpt":{"rendered":"
In one of my project I need to generate GSP (groovy server pages) on the fly and write them on the file system. There was a quartz job that updates the GSP page on regular intervals. The problem was, this functionality worked flawless in the development environment but fails in test and production environment. In […]<\/p>\n","protected":false},"author":5,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"iawp_total_views":5,"footnotes":""},"categories":[7],"tags":[],"class_list":["post-549","post","type-post","status-publish","format-standard","hentry","category-grails"],"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