java.lang.Objectorg.springframework.context.support.ApplicationObjectSupport
org.springframework.web.context.support.WebApplicationObjectSupport
org.springframework.web.servlet.view.AbstractView
All Implemented Interfaces:
View, BeanNameAware, ServletContextAware, ApplicationContextAware
Direct Known Subclasses:
AbstractXsltView, TilesView, XsltView, InternalResourceView, FreeMarkerView, AbstractTemplateView, JasperReportsMultiFormatView, TilesJstlView, JasperReportsPdfView, JasperReportsCsvView, VelocityLayoutView, AbstractJasperReportsView, JasperReportsXlsView, AbstractJasperReportsSingleFormatView, AbstractPdfView, VelocityView, AbstractJExcelView, AbstractUrlBasedView, ConfigurableJasperReportsView, JstlView, VelocityToolboxView, TilesView, JasperReportsHtmlView, AbstractExcelView, RedirectView
Provides support for static attributes, to be made available to the view, with a variety of ways to specify them. Static attributes will be merged with the given dynamic attributes (the model that the controller returned) for each render operation.
Extends WebApplicationObjectSupport , which will be helpful to some views. Subclasses just need to implement the actual rendering.
Rod - JohnsonJuergen - Hoeller| Field Summary | ||
|---|---|---|
| public static final String | DEFAULT_CONTENT_TYPE | Default content type. Overridable as bean property. |
| Fields inherited from org.springframework.context.support.ApplicationObjectSupport: |
|---|
| logger |
| Method from org.springframework.web.servlet.view.AbstractView Summary: |
|---|
| addStaticAttribute, createRequestContext, exposeModelAsRequestAttributes, generatesDownloadContent, getAttributesMap, getBeanName, getContentType, getRequestContextAttribute, getStaticAttributes, prepareResponse, render, renderMergedOutputModel, setAttributes, setAttributesCSV, setAttributesMap, setBeanName, setContentType, setRequestContextAttribute, toString |
| Methods from org.springframework.web.context.support.WebApplicationObjectSupport: |
|---|
| getServletContext, getTempDir, getWebApplicationContext, initApplicationContext, initServletContext, isContextRequired, setServletContext |
| Methods from org.springframework.context.support.ApplicationObjectSupport: |
|---|
| getApplicationContext, getMessageSourceAccessor, initApplicationContext, initApplicationContext, isContextRequired, requiredContextClass, setApplicationContext |
| Methods from java.lang.Object: |
|---|
| equals, getClass, hashCode, notify, notifyAll, toString, wait, wait, wait |
| Method from org.springframework.web.servlet.view.AbstractView Detail: |
|---|
"Static" attributes are fixed attributes that are specified in the View instance configuration. "Dynamic" attributes, on the other hand, are values passed in as part of the model. Must be invoked before any calls to |
Default implementation creates a standard RequestContext instance for the given request and model. Can be overridden in subclasses for custom instances. |
|
The default implementation returns |
Useful for specifying entries directly, for example via "attributesMap[myKey]". This is particularly useful for adding or overriding entries in child view definitions. |
null,
if the view was correctly configured. |
|
|
Returns an unmodifiable Map, as this is not intended for manipulating the Map but rather just for checking the contents. |
The default implementation applies a workaround for an IE bug when sending download content via HTTPS. |
|
The first step will be preparing the request: In the JSP case, this would mean setting model objects as request attributes. The second step will be the actual rendering of the view, for example including the JSP via a RequestDispatcher. |
java.util.Properties object.
"Static" attributes are fixed attributes that are specified in the View instance configuration. "Dynamic" attributes, on the other hand, are values passed in as part of the model. This is the most convenient way to set static attributes. Note that static attributes can be overridden by dynamic attributes, if a value with the same name is included in the model. Can be populated with a String "value" (parsed via PropertiesEditor) or a "props" element in XML bean definitions. |
"Static" attributes are fixed attributes that are specified in the View instance configuration. "Dynamic" attributes, on the other hand, are values passed in as part of the model. |
"Static" attributes are fixed attributes that are specified in the View instance configuration. "Dynamic" attributes, on the other hand, are values passed in as part of the model. Can be populated with a "map" or "props" element in XML bean definitions. |
Framework code must call this when constructing views. |
May be ignored by subclasses if the view itself is assumed to set the content type, e.g. in case of JSPs. |
|
|