|
The Spring Framework | |||||||||
PREV PACKAGE NEXT PACKAGE | FRAMES NO FRAMES |
See:
Description
Class Summary | |
---|---|
AbstractCachingViewResolver | Convenient base class for ViewResolver
implementations. |
AbstractTemplateView | AbstractTemplateView provides template based view technologies such as Velocity and FreeMarker, with the ability to use request and session attributes in their model and the option to expose helper objects for Spring's Velocity/FreeMarker macro library. |
AbstractTemplateViewResolver | Abstract base class for template view resolvers, in particular for Velocity and FreeMarker views. |
AbstractUrlBasedView | Abstract base class for URL-based views. |
AbstractView | Abstract base class for View
implementations. |
BeanNameViewResolver | Simple implementation of ViewResolver that interprets a view name as bean name in the current application context, i.e. in the XML file of the executing DispatcherServlet. |
DefaultRequestToViewNameTranslator | Simply transforms the URI of the incoming request into the 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, exposing all model attributes as HTTP query parameters. |
ResourceBundleViewResolver | ViewResolver implementation
that uses bean definitions in a ResourceBundle , specified by
the bundle basename. |
UrlBasedViewResolver | Simple implementation of the ViewResolver
interface, allowing for direct resolution of symbolic view names to URLs,
without explicit mapping definition. |
XmlViewResolver | Implementation of ViewResolver that uses bean definitions in an XML file, specified by resource location. |
Provides standard View and ViewResolver implementations, including abstract base classes for custom implementations.
Application developers don't usually need to implement views, as the framework provides standard views for JSPs, Velocity, 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.
|
The Spring Framework | |||||||||
PREV PACKAGE NEXT PACKAGE | FRAMES NO FRAMES |