See: Description
| Interface | Description |
|---|---|
| AbstractCachingViewResolver.CacheFilter |
Filter that determines if view should be cached.
|
| Class | Description |
|---|---|
| AbstractCachingViewResolver |
Convenient base class for
ViewResolver
implementations. |
| AbstractTemplateView |
Adapter base class for template-based view technologies such as FreeMarker,
with the ability to use request and session attributes in their model and
the option to expose helper objects for Spring's FreeMarker macro library.
|
| AbstractTemplateViewResolver |
Abstract base class for template view resolvers, in particular for FreeMarker views.
|
| AbstractUrlBasedView |
Abstract base class for URL-based views.
|
| AbstractView |
Abstract base class for
View
implementations. |
| BeanNameViewResolver |
A simple implementation of
ViewResolver
that interprets a view name as a bean name in the current application context,
i.e. |
| ContentNegotiatingViewResolver |
Implementation of
ViewResolver that resolves a view based on the request file name
or Accept header. |
| DefaultRequestToViewNameTranslator |
RequestToViewNameTranslator that simply transforms the URI of
the incoming request into a view name. |
| InternalResourceView |
Wrapper for a JSP or other resource within the same web application.
|
| InternalResourceViewResolver |
Convenient subclass of
UrlBasedViewResolver that supports
InternalResourceView (i.e. |
| JstlView |
Specialization of
InternalResourceView for JSTL pages,
i.e. |
| RedirectView |
View that redirects to an absolute, context relative, or current request
relative URL.
|
| ResourceBundleViewResolver | Deprecated
as of 5.3, in favor of Spring's common view resolver variants
and/or custom resolver implementations
|
| UrlBasedViewResolver |
Simple implementation of the
ViewResolver
interface, allowing for direct resolution of symbolic view names to URLs,
without explicit mapping definitions. |
| ViewResolverComposite |
A
ViewResolver that delegates to others. |
| XmlViewResolver | Deprecated
as of 5.3, in favor of Spring's common view resolver variants
and/or custom resolver implementations
|
Application developers don't usually need to implement views, as the framework provides standard views for JSPs, FreeMarker, XSLT, etc. However, the ability to implement custom views easily by subclassing the AbstractView class in this package can be very helpful if an application has unusual view requirements.