Package org.springframework.web.portlet.mvc

Standard controller implementations for the portlet MVC framework that comes with Spring.

See:
Description

Interface Summary

Controller

Base portlet Controller interface, representing a component that receives RenderRequest/RenderResponse and ActionRequest/ActionResponse like a Portlet but is able to participate in an MVC workflow.

Class Summary

AbstractCommandController	Abstract base class for custom command controllers.
AbstractController	Convenient superclass for controller implementations, using the Template Method design pattern.
AbstractFormController	Form controller that auto-populates a form bean from the request.
AbstractWizardFormController	Form controller for typical wizard-style workflows.
BaseCommandController	Controller implementation which creates an object (the command object) on receipt of a request and attempts to populate this object with request parameters.
ParameterizableViewController	Trivial controller that always returns a named view.
PortletModeNameViewController	Trivial controller that transforms the PortletMode to a view name.
PortletWrappingController	Controller implementation that wraps a portlet instance which it manages internally.
SimpleControllerHandlerAdapter	Adapter to use the Controller workflow interface with the generic DispatcherPortlet.
SimpleFormController	Concrete FormController implementation that provides configurable form and success views, and an onSubmit chain for convenient overriding.

Package org.springframework.web.portlet.mvc Description

Standard controller implementations for the portlet MVC framework that comes with Spring. Provides both abstract base classes and concrete implementations for often seen use cases.

A Controller - as defined in this package - is analogous to a Struts Action. Usually Controllers are JavaBeans to allow easy configuration using the org.springframework.beans package. Controllers define the C from so-called MVC paradigm and can be used in conjunction with the ModelAndView to achieve interactive applications. The view might be represented by a HTML interface, but, because of model and the controller being completely independent of the view, PDF views are possible, as well as for instance Excel views.

Especially useful to read, while getting into the Spring MVC framework are the following:

• Controller
• BaseCommandController
• ParameterizableViewController