What is Difference between Mvc1 architecture and Mvc2 Architecture?

  • Interview Candidate
  • 20
  • 26607

Showing Answers 1 - 20 of 20 Answers

Raja Sekhar

  • Oct 14th, 2005
 

Hi,MVC is a design pattern. It contains two models. MVC Model 1, MVC Model 2.Struts framework implements MVC Design Pattern. Struts can implement Model 1 and Model 2. Model 2 most properly describes the application of MVC in a Web-Application context.Following are the important feature of MVC1 architecture: (1) HTML or JSP files are used to code the presentation. JSP files use java beans to retrieve data if required.(2)MVC1 architecture is page-centric design all the business and processing logic means any JSP page can either present in the JSP or may be called directly from the JSP page.(3)Data access is usually done using Custom tag or through java bean call.Therefore we can say that in MVC1 there is tight coupling between page and model.Following are the important feature of MVC2 architecture(1)This architecture removes the page-centric property of MVC1 architecture by separating Presentation, Control logic and Application state(2)In MVC2 architecture there is one Controller which receive all request for the application and is responsible for taking appropriate action in response to each request. Second one is Model which is represented by JavaBeans, business object, and database. Third one is View or is JSP page it takes the information provided by Controller and Module and presents it to user.Raj

gudlarajesh

  • Nov 4th, 2005
 

what is the exact answer?

  Was this answer useful?  Yes

akash

  • Nov 7th, 2005
 

The main difference between MVC-I and MVC-II is

in MVC-I all the view,control elements are implemented using Servlets.

in MVC-II the view is implemented using JSP,and the controller is implemented using Servlets,as JSP provides better user interface than Servlets.

  Was this answer useful?  Yes

Ashok

  • Nov 22nd, 2005
 

Thanks to Raja for his answer.

  Was this answer useful?  Yes

suresh

  • Dec 16th, 2005
 

Can't we implement controller components with JSP?

  Was this answer useful?  Yes

catchsumang

  • Dec 28th, 2005
 

The main difference b/w MVC-1 ans MVC-2 is,MVC-1 is used for small scale applications and MVC-2 is used for large scale applications,in MVC-1 is used for small scale becoz the whole req n response is controled by JSP, but where as in MVC-2, request is taken by servlets n control is passed to JSP's or beans depending upon the request and response is given by JSP r any other view used.

  Was this answer useful?  Yes

yohannan

  • Jan 20th, 2006
 

MVC1 the controller is JSP, where as in MVC2 the contrller is servlet

  Was this answer useful?  Yes

dev

  • Feb 7th, 2006
 

raj nice answer tks a lot

  Was this answer useful?  Yes

suneel

  • May 15th, 2006
 

Raja Shekar,Thanks a lot for your answer. This is what an interviewer would expect.Thanks,Suneel

  Was this answer useful?  Yes

suneel

  • May 15th, 2006
 

You can look at http://www.javaworld.com/javaworld/jw-12-1999/jw-12-ssj-jspmvc.html for a clear discription with examples which corroborates raj shekar's answer.ThanksSuneel

  Was this answer useful?  Yes

vijay

  • Jul 21st, 2006
 

MVC1 was a first generation approach that used JSP pages and the JavaBeans component

architecture to implement the MVC architecture for the Web. As shown in Figure 8?2, HTTP

requests are sent to a JSP page that implements Controller logic and calls out to the ?Model?

for data to update the ?View.? This approach combines Controller and View functionality

within a JSP page and therefore breaks the MVC paradigm. MVC1 is appropriate for simple

development and prototyping. It is not, however, recommended for serious development.

 

The MVC2 architecture is actually a modified MVC implementation. The major modification

is that the Model no longer fires events to its Views.

The central issue is that the life cycle of the servlet (the Controller and View) is not

necessarily the life cycle of the application, as it is with desktop applications. The servlet

begins with a user request, typically generated by a Web browser, and ends with the

response. The Model, however, may, and typically does, persist across the life of multiple

servlets. Therefore, it cannot reliably notify View objects of internal state changes. This has

the following consequences:

The Model is now more ?generic,? because it no longer implements the logic for

registering and unregistering listeners, nor does it need to implement logic to generate

events.

The View is now responsible for capturing Model state changes.

The Controller now notifies the View of state changes to the Model.

The Controller must manipulate the Model before notifying the View.

 

  Was this answer useful?  Yes

Sreedhar Reddy

  • Aug 25th, 2006
 

Thank u Raj,ur Valueable answer.Sreedhar

  Was this answer useful?  Yes

Sreedhar Reddy

  • Aug 25th, 2006
 

Thanks Suman.Sreedhar

  Was this answer useful?  Yes

sudarvizhi kulothungan

  • Sep 5th, 2006
 

Hai,

 neatly explained.....i understood the concept clearly....

  Was this answer useful?  Yes

Amarnadh

  • Sep 26th, 2006
 

MVC1 architecture describes to implement controller and view responsibilities using jsp.MVC2 architecture describes to implement controller responsibility using servlet,and view responsibility using jsp.

  Was this answer useful?  Yes

Srinivas

  • Oct 6th, 2006
 

i'm a student want to know the answer for this question can anyone there help me ?

  Was this answer useful?  Yes

A Java developer

  • Dec 12th, 2006
 

The answers provided in this thread focus more on the current implementations of MVC1 and MVC2 and therefore are only partially correct.

The real difference between MVC models 1 and 2 is that in model 2 the Model, View and Controller should be coded as separate coding units (a.k.a. Java classes).  In model 1, they can all be a part of the same coding unit.

Now, going by the definition, it is not required for an MVC2 implementation to use Servlets for Controller and JSPs for Views.  One can as well use JSPs or Servlets throughout and still claim to be MVC2 compliant.  The important point is that in MVC2 different coding units should be used for M-V-C parts of the architecture.

Whether a solution which uses JSPs as Controller or Servlet as View would be a good, maintainable implementation is another question.  It is for this reason that the recommendation is to use JSPs for View and Servlets for Controller portions of the architecture.

  Was this answer useful?  Yes

sundarjothi

  • May 3rd, 2010
 

MVC1 combines presentation logic and business logic.
But not in MVC2.
MVC2 separates presentation logic and business logic(ex struts framework).

  Was this answer useful?  Yes

Zahid Nasim

  • Jul 20th, 2011
 

Raja Shekhar is given a good difference between MVC1 and MVCII.

See In short,

MVC1 (Model 1) = JSP as "V" and "C", JavaBean as "M"
MVC2 (Model 2) = Servlet as "C", JSP as "V", JavaBean as "M"

  Was this answer useful?  Yes

narendrakumar

  • Oct 4th, 2012
 

For small scale projects use MVC1 for large scale projects use MVC2
Because
In MVC1 both view and controller implemented in servlets
In MVC2 view implemented in JSP and controller implemented in servlets(JSP provides more user interface than servlets)

In MVC1 use more controllers for all request processing But in MVC2 we are using only one controller to process all requests


  Was this answer useful?  Yes

Give your answer:

If you think the above answer is not correct, Please select a reason and add your answer below.

 

Related Answered Questions

 

Related Open Questions