VelocityLayoutView emulates the functionality offered by Velocity's
VelocityLayoutServlet to ease page composition from different templates.
The url property should be set to the content template
for the view, and the layout template location should be specified as
layoutUrl property. A view can override the configured
layout template location by setting the appropriate key (the default
is "layout") in the content template.
When the view is rendered, the VelocityContext is first merged with
the content template (specified by the url property) and
then merged with the layout template to produce the final output.
The layout template can include the screen content through a
VelocityContext variable (the default is "screen_content").
At runtime, this variable will contain the rendered content template.
checkTemplate()
Overrides VelocityView.checkTemplate() to additionally check
that both the layout template and the screen content template can be loaded.
protected void
doRender(org.apache.velocity.context.Context context,
HttpServletResponse response)
Overrides the normal rendering process in order to pre-process the Context,
merging it with the screen template into a single value (identified by the
value of screenContentKey).
void
setLayoutKey(String layoutKey)
Set the context key used to specify an alternate layout to be used instead
of the default layout.
Set the context key used to specify an alternate layout to be used instead
of the default layout. Screen content templates can override the layout
template that they wish to be wrapped with by setting this value in the
template, for example: #set( $layout = "MyLayout.vm" )
The default key is "layout", as illustrated above.
Parameters:
layoutKey - the name of the key you wish to use in your
screen content templates to override the layout template
setScreenContentKey
public void setScreenContentKey(String screenContentKey)
Set the name of the context key that will hold the content of
the screen within the layout template. This key must be present
in the layout template for the current screen to be rendered.
Default is "screen_content": accessed in VTL as
$screen_content.
Parameters:
screenContentKey - the name of the screen content key to use
Overrides VelocityView.checkTemplate() to additionally check
that both the layout template and the screen content template can be loaded.
Note that during rendering of the screen content, the layout template
can be changed which may invalidate any early checking done here.
Overrides the normal rendering process in order to pre-process the Context,
merging it with the screen template into a single value (identified by the
value of screenContentKey). The layout template is then merged with the
modified Context in the super class.