| org.riotfamily.common.web.view.freemarker.RiotFreeMarkerView
All known Subclasses: org.riotfamily.components.view.ComponentFreeMarkerView,
RiotFreeMarkerView | public class RiotFreeMarkerView extends FreeMarkerView (Code) | | Differences to Spring's FreeMarkerView:
- Model attributes may override attributes from the request or the session
- The plain HttpServletRequest object is exposed under the key "request"
- The model is not exposed to the request, unless the
RiotFreeMarkerView.setFreeMarkerServletMode(boolean) freeMarkeServletMode is enabled
- Provides the possibility to create stateful macro helpers via the
MacroHelperFactory interface
|
MODEL_ATTRIBUTE | final public static String MODEL_ATTRIBUTE(Code) | | |
TEMPLATE_NAME_KEY | final public static Object TEMPLATE_NAME_KEY(Code) | | |
setAllowModelOverride | public void setAllowModelOverride(boolean allowModelOverride)(Code) | | Sets whether the model may contain keys that are also present as request
or session attributes. Otherwise an exception will be thrown when Spring
tries to expose an attribute that conflicts with a key in the model.
|
setFreeMarkerServletMode | public void setFreeMarkerServletMode(boolean freeMarkerServletMode)(Code) | | Sets whether the view should mimic the behavior of the
FreemarkerServlet , i.e. provide support JSP tag libraries, the
"Request", "Session" and "Application" HashModels. By default this
mode is disabled, mainly because JSP support requires exposure of the
model as separate request attributes, which can be quite confusing when
working with nested views.
Parameters: freeMarkerServletMode - |
setMacroHelperFactories | public void setMacroHelperFactories(Map macroHelperFactories)(Code) | | Sets a Map of
MacroHelperFactory instances keyed by the
variable name under which the created helper should be exposed.
|
|
|