java.lang.Object
   org.springframework.context.support.ApplicationObjectSupport
      org.springframework.web.context.support.WebApplicationObjectSupport
         org.springframework.web.servlet.support.WebContentGenerator
            org.springframework.web.servlet.mvc.AbstractController
               org.springframework.web.servlet.mvc.ParameterizableViewController

All Implemented Interfaces:
    Controller, ServletContextAware, ApplicationContextAware

Trivial controller that always returns a named view. The view can be configured using an exposed configuration property. This controller offers an alternative to sending a request straight to a view such as a JSP. The advantage here is that the client is not exposed to the concrete view technology but rather just to the controller URL; the concrete view will be determined by the ViewResolver.

An alternative to the ParameterizableViewController is a MultiActionController , which can define a variety of handler methods that just return a plain ModelAndView instance for a given view name.

Workflow (and that defined by superclass):

1. Request is received by the controller
2. call to handleRequestInternal which just returns the view, named by the configuration property viewName. Nothing more, nothing less

Exposed configuration properties (and those defined by superclass):

name	default	description
viewName	null	the name of the view the viewResolver will use to forward to (if this property is not set, an exception will be thrown during initialization)

author: Rod - Johnson

author: Juergen - Hoeller

 public String getViewName() 
{
		return this.viewName;
}

 protected ModelAndView handleRequestInternal(HttpServletRequest request,
    HttpServletResponse response) throws Exception 
{
		return new ModelAndView(getViewName());
}

 protected  void initApplicationContext() 
{
		if (this.viewName == null) {
			throw new IllegalArgumentException("Property 'viewName' is required");
		}
}

 public  void setViewName(String viewName) 
{
		this.viewName = viewName;
}