In your application, once the service have handled the request and returned the results desired, you will need to render the results in a useful manner to the user. This is the purpose of viewing technology such as JavaServer Pages (JSP). Although you can use JSPs in Spring there are a number of other viewing technologies that Spring support. In this tip, I will outline some of the other view technologies that are available.
When Spring is looking to render some content, the DispatcherServlet
In my previous tips, I looked out how to make the key RESTful method calls. In all of them the controller’s handler method finishes, and a logical view name is usually returned. In the case that the method doesn’t return a logical view name (a method returning void) then the logical view name is derived from the request’s URL. The DispatcherServlet passes the view name to a view resolver in order to facilitate the determination of which view should render the results of the request.
Updated 11-30-2011 at 01:42 PM by Spring Framework
Following on from my previous tip, I will now define the page view from our previous tip. Using Tiles properly, the home page is composed of several distinct pieces. The main_template.jsp file describes the common layout for all pages in the Springexample application, while home.jsp displays the main content for the home page. Plus, carForm.jsp and login.jsp provide additional common elements.
The home.jsp is where the home page request finishes its journey. It picks up the list of Cars