4/22/13Model 1 and Model 2 (MVC) Architecture - javatpoint New: JAXB | Junit Advertise Us | Ask Question | forum | login| Home Core Java Servlet JSP Struts2 Mail API Hibernate Spring Android Quiz Projects Interview Q Comment Forum Basics of Struts2 Struts Model1 vs Model2 Struts2 Features Steps to create Struts2 application Struts2 in Myeclipse Core Components Interceptors ValueStack ActionContext ActionInvocation OGNL Struts 2 Flow Struts2 Action Struts2 Configuration multi configuration multi namespace Interceptors params interceptor intermediate result preparation logic ModelDriven Exception Handling Custom Interceptor Struts 2 Validation Custom Validation Input Validation Ajax Validation Aware Interfaces ServletActionContext SessionAware ServletContextAware Struts2 with I18N Zero Configuration By convention By annotation Struts2 with Tiles2 Hibernate with Struts2 Spring with Struts2 Development Registration Example Login and Logout Fetch All Records Model 1 and Model 2 (MVC) Architecture Before developing the web applications, we need to have idea about design models. There are two types of programming models (design models) 1. Model 1 Architecture 2. Model 2 (MVC) Architecture <<prev next>> Model 1 and Model 2 (MVC) Architecture Model 1 Architecture Model 2 (MVC) Architecture Model 1 Architecture Servlet and JSP are the main technologies to develop the web applications. Servlet was considered superior to CGI. Servlet technology doesn't create process, rather it creates thread to handle request. The advantage of creating thread over process is that it doesn't allocate separate memory area. Thus many subsequent requests can be easily handled by servlet. Problem in Servlet technology Servlet needs to recompile if any designing code is modified. It doen't provide separation of concern. Presentation and Business logic are mixed up. JSP overcomes almost all the problems of Servlet. It provides better separation of concern, now presentation and business logic can be easily separated. You don't need to redeploy the application if JSP page is modified. JSP provides support to develop web application using JavaBean, custom tags and JSTL so that we can put the business logic separate from our JSP that will be easier to test and debug. As you can see in the above figure, there is picturized the flow of the model1 architecture. 1. Browser sends request for the JSP page 2. JSP accesses Java Bean and invokes business logic 3. Java Bean connects to the database and get/save data 4. Response is sent to the browser which is generated by JSP Advantage of Model 1 Architecture Easy and Quick to develop web application Disadvantage of Model 1 Architecture Navigation control is decentralized since every page contains the logic to determine the next page. If JSP page name is changed that is referred by other pages, we need to change it in all the pages that leads to the maintenance problem. Time consuming You need to spend more time to develop custom tags in JSP. So that we don't need to use scriptlet tag. Hard to extend It is better for small applications but not for large applications. Model 2 (MVC) Architecture Model 2 is based on the MVC (Model View Controller) design pattern. The MVC design pattern consists of three modules model, view and controller. Model The model represents the state (data) and business logic of the application. View The view module is responsible to display data i.e. it represents the presentation. Controller The controller module acts as an interface between view and model. It intercepts all the www.javatpoint.com/model-1-and-model-2-mvc-architecture 1/3 Solution of Model 2 Architecture: Configurable MVC Components It uses the declarative approach for defining view components.com. Visit here to get the Example of MVC using Servlet and JSP.4/22/13 Controller The controller module acts as an interface between view and model.com/model-1-and-model-2-mvc-architecture 2/3 . www. <<prev next>> 544 36 6 Google + 0 Tw eet 71 Like 7.526 people like javatpoint. receives input and commands to Model / View to change accordingly. we define all the action classes and view components in struts.5k 5 javatpoint.e. Model 1 and Model 2 (MVC) Architecture .xml file. request mapping etc. we need to recompile the class and redeploy the application. The Struts framework provides the configurable MVC support. In struts 2. It intercepts all the requests i.com Like 7. It resolves the problem of Model 2 architecture. If we change the controller code.javatpoint Advantage of Model 2 (MVC) Architecture Navigation control is centralized Now only controller contains the logic to determine the next page. Easy to maintain Easy to extend Easy to test Better separation of concerns Disadvantage of Model 2 (MVC) Architecture We need to write the controller code self.javatpoint. We provide assurance of 90% interview questions.javatpoint. please mail to sonoojaiswal1987@gmail. www.com or sonoojaiswal@javatpoint. Copyright 2011-2012.javatpoint F acebook social plugin Like the www.com.javatpoint. Tutorials and examples are constantly reviewed to avoid errors.com/model-1-and-model-2-mvc-architecture 3/3 .4/22/13 Model 1 and Model 2 (MVC) Architecture .com on facebook / google+ / twitter / subscribe to get latest updates Sitemap javatpoint. you agree to have read and accepted our terms of use and privacy policy. All Rights Reserved. Examples might be simplified to improve reading and basic understanding. While using this site. but we cannot warrant full correctness of all content. If there is any mistake.com is developed Core Java Servlet JSP Struts2 Hibernate Spring Android Interview Questions to provide easy and point to point learning and training in detail.
Report "Model 1 and Model 2 (MVC) Architecture - Javatpoint"