Now, let us check the required configuration for HelloWeb-servlet.xml file, placed in your web application's WebContent/WEB-INF directory −įollowing are the important points about HelloWeb-servlet.xml file − If you do not want to go with default filename as -servlet.xml and default location as WebContent/WEB-INF, you can customize this file name and location by adding the servlet listener ContextLoaderListener in your web.xml file as follows − jsp will be handled by the HelloWeb DispatcherServlet. Next, tag indicates what URLs will be handled by which DispatcherServlet. In this case, our file will be HelloWebservlet.xml.
Upon initialization of HelloWeb DispatcherServlet, the framework will try to load the application context from a file named -servlet.xml located in the application's WebContent/WEB-INF directory. The web.xml file will be kept in the WebContent/WEB-INF directory of your web application. The following is an example to show declaration and mapping for HelloWeb DispatcherServlet example − You need to map requests that you want the DispatcherServlet to handle, by using a URL mapping in the web.xml file. HandlerMapping, Controller, and ViewResolver are parts of WebApplicationContext which is an extension of the plain ApplicationContext with some extra features necessary for web applications. Once view is finalized, The DispatcherServlet passes the model data to the view which is finally rendered on the browser.Īll the above-mentioned components, i.e. The DispatcherServlet will take help from ViewResolver to pickup the defined view for the request. The service method will set model data based on defined business logic and returns view name to the DispatcherServlet. The Controller takes the request and calls the appropriate service methods based on used GET or POST method. The request processing workflow of the Spring Web MVC DispatcherServlet is illustrated in the following diagram −įollowing is the sequence of events corresponding to an incoming HTTP request to DispatcherServlet −Īfter receiving an HTTP request, DispatcherServlet consults the HandlerMapping to call the appropriate Controller. The Spring Web model-view-controller (MVC) framework is designed around a DispatcherServlet that handles all the HTTP requests and responses.
The Controller is responsible for processing user requests and building an appropriate model and passes it to the view for rendering. The View is responsible for rendering the model data and in general it generates HTML output that the client's browser can interpret. The Model encapsulates the application data and in general they will consist of POJO. The MVC pattern results in separating the different aspects of the application (input logic, business logic, and UI logic), while providing a loose coupling between these elements. The Spring Web MVC framework provides Model-View-Controller (MVC) architecture and ready components that can be used to develop flexible and loosely coupled web applications.
0 kommentar(er)
