What is the difference between mvc1 and mvc2 architecture

Difference Between Similar Terms and Objects. MLA 8 Franscisco,. Name required. Email required. Please note: comment moderation is enabled and may delay your comment.

There is no need to resubmit your comment. Notify me of followup comments via e-mail. Written by : Celine. Company Questions. Artificial Intelligence. Cloud Computing. Data Science. Angular 7. Machine Learning. Data Structures. Operating System. Computer Network. Compiler Design. Computer Organization. Discrete Mathematics. Ethical Hacking. Computer Graphics. Software Engineering. Web Technology. Cyber Security. C Programming.

You cannot have complex business logic in your JSP, thats bad practice. Ideally in MVC there are JSP pages to handle the presentation logic, the model to encapsulate business data and manipulation logic and a controller to co-ordinate between the view and model.

MVC is an architecture for Application development in general. It is not specific to Desktop Applications or Web Applications. MVC was designed considering the scalability aspect of an application development architecture which implements the clearest possible separation of concerns among its components so as to produce a well de-coupled and highly extensible Application as a result.

The scenario is dreaded for the simple fact that most of the business logic is exposed to the world and with raising complexity of the application, the problems of handling the various flows grow enormously. This happens to be the page-centric design which is flawed when it comes to developing scalable applications. The simplicity being one single place for handling most of your logic. In a nutshell: Model 1 doesn't have a controller to dispatch requests, Model 2 does.

While in MVC2 controller is servlet and model is java class. In MVC1 there is tight coupling between page and model as data access is usually done using Custom tag or through java bean call. In MVC2 architecture there is only one controller which receives all the request for the application and is responsible for taking appropriate action in response to each request. MVC1 is appropriate for simple development and prototyping.

It is not, however, recommended for serious development. The hallmark of the MVC2 approach is the separation of Controller code from content.

Implementations of presentation frameworks such as Struts, adhere to the MVC2 approach. Stack Overflow for Teams — Collaborate and share knowledge with a private group. Create a free Team What is Teams? Collectives on Stack Overflow.