@groovy.transform.CompileStatic class GrailsSiteMeshViewResolverBeanPostProcessor extends SiteMeshViewResolverBeanPostProcessor
SiteMeshViewResolverBeanPostProcessor preconfigured to wrap
Grails' gspViewResolver bean with a
GrailsSiteMeshViewResolver.
| Modifiers | Name | Description |
|---|---|---|
static java.lang.String |
TARGET_VIEW_RESOLVER_BEAN_NAME |
The primary GSP view resolver bean name in Grails. |
| Constructor and description |
|---|
GrailsSiteMeshViewResolverBeanPostProcessor() |
| Type Params | Return Type | Name and description |
|---|---|---|
|
void |
afterSingletonsInstantiated()The upstream implementation already suppresses its zero-wrap startup warning when the target resolves to a org.sitemesh.webmvc.SiteMeshViewResolver (the definition-level wrap applied by Sitemesh3ViewResolverDefinitionPostProcessor); the only Grails addition is silence when the SiteMesh 2 module owns decoration. |
|
java.lang.Object |
postProcessAfterInitialization(java.lang.Object bean, java.lang.String beanName)Contexts can include this post-processor (via Sitemesh3AutoConfiguration)
without the SiteMesh plugin beans being registered — the unit-test context built
by grails-testing-support registers all Grails auto-configurations but never runs
the plugin's bean registrations. |
The primary GSP view resolver bean name in Grails. The historical
name jspViewResolver is kept for compatibility with the
plugin's GroovyPagesPostProcessor, which registers the GSP
resolver under that name when it isn't already present (see
org.grails.plugins.web.GroovyPagesPostProcessor). The
modern GspAutoConfiguration.gspViewResolver() bean is
aliased to this name too when it fires.
The upstream implementation already suppresses its zero-wrap startup warning when the target resolves to a org.sitemesh.webmvc.SiteMeshViewResolver (the definition-level wrap applied by Sitemesh3ViewResolverDefinitionPostProcessor); the only Grails addition is silence when the SiteMesh 2 module owns decoration.
Contexts can include this post-processor (via Sitemesh3AutoConfiguration)
without the SiteMesh plugin beans being registered — the unit-test context built
by grails-testing-support registers all Grails auto-configurations but never runs
the plugin's bean registrations. Decoration is impossible without those beans,
so leave the view resolver unwrapped instead of failing the context.