We have a setup where a backend thread, fired by the Spring Events, does some processing, generates a PDF and emails the result to the user.
\nThe code we were using to generate the HTML from a GSP to be converted to a PDF using iText was as follows :<\/p>\n
[java]
\n def webRequest = RequestContextHolder.getRequestAttributes()
\n def originalOut = webRequest.out
\n try {
\n def sw = new StringWriter()
\n def pw = new PrintWriter(sw)
\n webRequest.out = pw
\n groovyPagesTemplateEngine.createTemplate("path_to_gsp").make([model:model]).writeTo(pw)
\n return sw.toString()
\n } finally {
\n webRequest.out = originalOut
\n }
\n[\/java]<\/p>\n
There was the obvious fallibility of this code that there was no Current Request associated with the backend thread!<\/p>\n
After doing some googling around it, I came across a few threads and posts which talked about Request Mocking, which has been used in Grails Template Engine Plugin. \u00a0We overcame this by using the code snippet given below to mock the web request<\/p>\n
[java]
\ndef webRequest = RequestContextHolder.getRequestAttributes()
\nif(!webRequest) {
\n def servletContext \u00a0= ServletContextHolder.getServletContext()
\n def applicationContext = WebApplicationContextUtils.getRequiredWebApplicationContext(servletContext)
\n webRequest = grails.util.GrailsWebUtil.bindMockWebRequest(applicationContext)
\n}
\n[\/java]<\/p>\n
However, things didn’t end there. This code broke while working on a WAR environment. The problem was that the MockWebRequest class was part of the “org.springframework:org.springframework.test:3.0.3.RELEASE” jar and had to be included in the BuildConfig.groovy as<\/p>\n
[java]<\/p>\n
dependencies{<\/p>\n
runtime ‘org.springframework:org.springframework.test:3.0.3.RELEASE’<\/p>\n
}<\/p>\n
[\/java]<\/p>\n
Ensure that the line<\/p>\n
[java]<\/p>\n
mavenCentral()<\/p>\n
[\/java]<\/p>\n
is not commented<\/span> in BuildConfig.groovy<\/p>\n We were working on Grails 1.3.4<\/p>\n <\/p>\n Hope this helps. We have a setup where a backend thread, fired by the Spring Events, does some processing, generates a PDF and emails the result to the user. The code we were using to generate the HTML from a GSP to be converted to a PDF using iText was as follows : [java] def webRequest = RequestContextHolder.getRequestAttributes() […]<\/p>\n","protected":false},"author":10,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"iawp_total_views":5,"footnotes":""},"categories":[7],"tags":[4840,9,32,292,4841,484],"class_list":["post-2478","post","type-post","status-publish","format-standard","hentry","category-grails","tag-grails","tag-groovy","tag-gsp","tag-pdf","tag-spring","tag-web-request-mocking"],"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
\nVivek<\/p>\n","protected":false},"excerpt":{"rendered":"