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.
Controller - as defined in this package - is analogous to a Struts
Controllers are JavaBeans
to allow easy configuration using the
package. Controllers define the
C from so-called MVC paradigm
and can be used in conjunction with the
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
Especially useful to read, while getting into the Spring MVC framework are the following:
|Controller||Base portlet Controller interface, representing a component that receives
RenderRequest/RenderResponse and ActionRequest/ActionResponse like a
|EventAwareController||Extension of the Portlet
|ResourceAwareController||Extension of the Portlet
|AbstractCommandController||This class is deprecated. as of Spring 3.0, in favor of annotated controllers|
|AbstractController||Convenient superclass for controller implementations, using the Template Method design pattern.|
|AbstractFormController||This class is deprecated. as of Spring 3.0, in favor of annotated controllers|
|AbstractWizardFormController||This class is deprecated. as of Spring 3.0, in favor of annotated controllers|
|BaseCommandController||This class is deprecated. as of Spring 3.0, in favor of annotated controllers|
Trivial controller that always returns a named view.
Trivial controller that transforms the PortletMode to a view name.
|SimpleControllerHandlerAdapter||Adapter to use the Controller workflow interface with the generic DispatcherPortlet.|
|SimpleFormController||This class is deprecated. as of Spring 3.0, in favor of annotated controllers|