(Quick Reference)
afterInterceptor
Purpose
Allows interception of actions after they have executed, but before the view is rendered.
Examples
Using a block:
class BookController {
def afterInterceptor = { model ->
model.foo = "bar"
}
}In this example we use a more fine-grained approach, using a Groovy method pointer to specify a helper method to use and a list of action names to be intercepted:
class BookController { def afterInterceptor = [action: this.&invokeMe, only: ['list']] private invokeMe(model) {
model.foo = "bar"
} def list() {
[bookList: Book.list()]
}
}In this example we use the Map syntax to constraint the
afterInterceptor to execute
only for the
list action.
Description
To define an interceptor that is executed after an action use the
afterInterceptor property:
def afterInterceptor = { model ->
println "Tracing action ${actionUri}"
}The first argument of the
Closure is the model
Map that resulted from the action that executed and will be passed to the view. This lets you manipulate the model before rendering the view. The model might be empty but will not be
null.
An
afterInterceptor may also inspect or modify the Spring MVC
ModelAndView object prior to rendering. In this case, the example becomes:
def afterInterceptor = { model, modelAndView ->
println "Current view is ${modelAndView.viewName}"
if (model.someVar) {
modelAndView.viewName = "/mycontroller/someotherview"
}
println "View is now ${modelAndView.viewName}"
}This allows the view to be changed based on the model returned by the current action. Note that the
modelAndView may be
null if the action being intercepted called
redirect or
render.
This example limited the intercepted actions using the
only argument but the
except argument can also be used to list the actions to not intercept, rather than those to intercept.
