@groovy.util.logging.Slf4j class GroovyPagesGrailsPlugin extends Plugin
Sets up and configures the GSP and GSP tag library support in Grails.
| Modifiers | Name | Description |
|---|---|---|
static java.lang.String |
GSP_RELOAD_INTERVAL |
|
static java.lang.String |
GSP_VIEWS_DIR |
| Type | Name and description |
|---|---|
java.lang.Object |
dependsOn |
java.lang.Object |
grailsVersion |
java.lang.Object |
loadAfter |
java.lang.Object |
observe |
java.lang.Object |
providedArtefacts |
java.lang.Object |
watchedResources |
| Properties inherited from class | Properties |
|---|---|
class Plugin |
applicationContext, artefacts, environment, grailsApplication, plugin, pluginManager |
| Constructor and description |
|---|
GroovyPagesGrailsPlugin() |
| Type Params | Return Type | Name and description |
|---|---|---|
|
BeanRegistrar |
beanRegistrar()Tag library beans autowire by name and are read from the artefacts the application knows about, which the org.springframework.beans.factory.BeanRegistry API cannot express, so their definitions are contributed by a dedicated post-processor. |
|
void |
doWithApplicationContext()Clear the page cache with the ApplicationContext is loaded |
|
groovy.lang.Closure |
doWithSpring()Configures the various Spring beans required by GSP |
|
protected boolean |
isDevelopmentMode()Whether the application is being developed, which decides where its pages are read from and whether they are watched for change. |
|
void |
onChange(java.util.Map<java.lang.String, java.lang.Object> event) |
|
void |
onConfigChange(java.util.Map<java.lang.String, java.lang.Object> event) |
|
static java.lang.String |
transformToValidLocation(java.lang.String location) |
| Methods inherited from class | Name |
|---|---|
class Plugin |
beanRegistrar, beans, doWithApplicationContext, doWithDynamicMethods, doWithSpring, doWithSpring, getApplicationContext, getConfig, getManager, onChange, onConfigChange, onShutdown, onStartup, setApplicationContext |
Tag library beans autowire by name and are read from the artefacts the application knows
about, which the org.springframework.beans.factory.BeanRegistry API cannot express, so
their definitions are contributed by a dedicated post-processor. Contributing them here rather
than from doWithSpring() leaves the definitions an ahead-of-time image generated, and
the injection generated with them, in place.
Clear the page cache with the ApplicationContext is loaded
Configures the various Spring beans required by GSP
Whether the application is being developed, which decides where its pages are read from and whether they are watched for change.
While code is being generated the answer is no, whatever the machine doing the generating looks like. Generation runs in the project directory, so a development environment is available there and the question would otherwise be answered for the machine that built the application rather than the one that runs it: the pages would be read from a directory that exists only on the build machine, whose path would be written into the artifact, and an image cannot compile a page it finds there in any case.