org.springframework.web.servlet.view Documentation Differences

This file contains all the changes in documentation in the package org.springframework.web.servlet.view as colored differences. Deletions are shown like this, and additions are shown like this.

If no deletions or additions are shown in an entry, the HTML tags will be what has changed. The new HTML tags are shown in the differences. If no documentation existed, and then some was added in a later version, this change is noted in the appropriate class pages of differences, but the change is not shown on this page. Only changes in existing text are shown here. Similarly, documentation which was inherited from another class or interface is not shown here.

Note that an HTML error in the new documentation may cause the display of other documentation changes to be presented incorrectly. For instance, failure to close a <code> tag will cause all subsequent paragraphs to be displayed differently.

Enable or disable caching.

This is equivalent to setting the "cacheLimit" property to the default limit (1024) or to 0, respectively.

Default is "true": caching is enabled. Disable this only for debugging and development. Warning: Disabling caching can severely impact performance.

Determines the list of MediaType for the given HttpServletRequest. The default implementation invokes .getMediaTypeFromFilename(String) if #setFavorPathExtension favorPathExtension property is true. If the property is false, or when a media type cannot be determined from the request path, this method will inspect the {@code Accept} header of the request. This method can be overridden to provide a different algorithm. @param request the current servlet request @return the list of media types requested, if any

View that redirects to an absolute, context relative, or current request relative URL. The URL may be a URI template in which case the URI template variables will be replaced with values available in the model. By default all primitive model attributes (or collections thereof) are exposed as HTTP query parameters (assuming they've not been used as URI template variables), but this behavior can be changed by overriding the .isEligibleProperty(String, Object) method.

A URL for this view is supposed to be a HTTP redirect URL, i.e. suitable for HttpServletResponse's sendRedirect method, which is what actually does the redirect if the HTTP 1.0 flag is on, or via sending back an HTTP 303 code - if the HTTP 1.0 compatibility flag is off.

Note that while the default value for the "contextRelative" flag is off, you will probably want to almost always set it to true. With the flag off, URLs starting with "/" are considered relative to the web server root, while with the flag on, they are considered relative to the web application root. Since most web applications will never know or care what their context path actually is, they are much better off setting this flag to true, and submitting paths which are to be considered relative to the web application root.

NOTE when using this redirect view in a Portlet environment: Make sure that your controller respects the Portlet sendRedirect constraints. When e.g. using org.springframework.web.portlet.mvc.SimpleFormController, make sure to set your controller's "redirectAction" property to "true", in order to make the controller base class behave accordingly. @author Rod Johnson @author Juergen Hoeller @author Colin Sampaleanu @author Sam Brannen @author Arjen Poutsma @author Rossen Stoyanchev @see #setContextRelative @see #setHttp10Compatible @see #setExposeModelAttributes @see javax.servlet.http.HttpServletResponse#sendRedirect

Whether to treat the redirect URL as a URI template. Set this flag to false if the redirect URL contains open and close curly braces "{", "}" and you don't want them interpreted as URI variables.

Defaults to true. @param expandUriTemplateVariables