MVC:
A classic design pattern where there exist three seperate architecture
elements:
- A Controller. This processes user input and makes decisions on,
among other things, what to do with the input.
- A Model. This generally is a memory-persistent representation of the
business system. It may also be all stored in a database or somewhere else.
- A View. This piece is what is displayed to the user.
The user generates input which is captured by the controller. The
controller updates one or more models and then
directs a view to be displayed to the user.
MVC2 (probably you mean "JSP - Model 2", or just "Model 2"):
This is an MVC approach to using JSP. In fact, the Struts user guide
(section 1.1) states, "It is now commonplace to use the terms Model 2 and
MVC interchangeably".
A good description of this architecture was delivered in 1999 at Java
One. I was first introduced to this approach to JSP development by reading
this article which was published at the conference. I think it's still
relevant today:
http://www.javaworld.com/javaworld/jw-12-1999/jw-12-ssj-jspmvc_p.html
GoF:
"Design Patterns: elements of reusable object-oriented software"
by Erich Gamma, Richard Helm, Ralph Johnson, John Vlissides (aka, the GoF)
pub 1995, ISBN 0-201-63361-2
The classic book on design patterns. Don't call yourself an architect if you don't
have it.
FWIW -
Kevin
Ida D�rum <[EMAIL PROTECTED]> on 04/29/2002 12:42:23 PM
Please respond to "Struts Users Mailing List"
<[EMAIL PROTECTED]>
To: "Struts Users Mailing List" <[EMAIL PROTECTED]>
cc: (bcc: Kevin Bedell/Systems/USHO/SunLife)
Subject: RE: Difference between MVC and MVC2 architectures
Gang of Four.
-----Original Message-----
From: Eddie Bush [mailto:[EMAIL PROTECTED]]
Sent: 29. april 2002 18:29
To: Struts Users Mailing List
Subject: Re: Difference between MVC and MVC2 architectures
GoF? Forgive me, but I don't know that one.
----- Original Message -----
From: "Chappell, Simon P" <[EMAIL PROTECTED]>
To: "Struts Users Mailing List" <[EMAIL PROTECTED]>
Sent: Monday, April 29, 2002 11:30 AM
Subject: RE: Difference between MVC and MVC2 architectures
Mark: Snap out of it! That was far too polite and informative! I noticed
that you provided an appropriate URL! ;-) There are standards to be kept
here. Next, you'll be suggesting that the person asking the question might
care to read the GoF and even provide them the appropriate page number!
Simon
>-----Original Message-----
>From: Galbreath, Mark [mailto:[EMAIL PROTECTED]]
>Sent: Monday, April 29, 2002 11:21 AM
>To: 'Struts Users Mailing List'
>Subject: RE: Difference between MVC and MVC2 architectures
>
>
>There's no such thing as "MVC-2" (it's "Model 2") and it's not an
>architecture; it's a design pattern. Further, what little difference
>between the two is thoroughly explained on the first page of
>jakarta.apache.org/struts.
>
>Mark
>
>-----Original Message-----
>From: bhatia10 [mailto:[EMAIL PROTECTED]]
>Sent: Monday, April 29, 2002 12:11 PM
>To: Struts Users Mailing List
>Subject: Difference between MVC and MVC2 architectures
>
>
>What is the difference between a MVC and MVC-2 architectures. How does
>Struts satisfy the MVC-2 architecture and why is it not just the MVC
>architecture.
>
>I would appreciate it if someone cud explain this briefy.
>
>Regards.
>
>
>
>--
>To unsubscribe, e-mail:
><mailto:[EMAIL PROTECTED]>
>For additional commands, e-mail:
><mailto:[EMAIL PROTECTED]>
>
>--
>To unsubscribe, e-mail:
<mailto:[EMAIL PROTECTED]>
For additional commands, e-mail:
<mailto:[EMAIL PROTECTED]>
--
To unsubscribe, e-mail:
<mailto:[EMAIL PROTECTED]>
For additional commands, e-mail:
<mailto:[EMAIL PROTECTED]>
--
To unsubscribe, e-mail: <
mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <
mailto:[EMAIL PROTECTED]>
--
To unsubscribe, e-mail: <
mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <
mailto:[EMAIL PROTECTED]>
---------------------------------------------------------------------------
This e-mail message (including attachments, if any) is intended for the use
of the individual or entity to which it is addressed and may contain
information that is privileged, proprietary , confidential and exempt from
disclosure. If you are not the intended recipient, you are notified that
any dissemination, distribution or copying of this communication is
strictly prohibited. If you have received this communication in error,
please notify the sender and erase this e-mail message immediately.
---------------------------------------------------------------------------
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
