MVC Pattern - Revision history

Suhridk at 06:39, 9 June 2013

2013-06-09T06:39:12Z

Suhridk: /* Controller */

2013-06-09T06:35:07Z

Controller

Suhridk: /* Model */

2013-06-09T06:32:45Z

Model

Suhridk: /* Intro */

2013-06-09T06:28:59Z

Intro

Suhridk at 06:25, 9 June 2013

2013-06-09T06:25:58Z

Suhridk: Created page with "= Model = * The model holds all data, state and application logic. The model is '''oblivious''' to the view and controller, although it provides an interface to manipulate and r..."

2012-06-13T20:07:44Z

Created page with "= Model = * The model holds all data, state and application logic. The model is '''oblivious''' to the view and controller, although it provides an interface to manipulate and r..."

New page

= Model =

* The model holds all data, state and application logic. The model is '''oblivious''' to the view and controller, although it provides an interface to manipulate and retrieve its state and can send notifications of state changes to observers.

= View =

* Gives a representation of the model. The view usually gets the state and data it needs to display directly from the model.

= Controller =

* Takes the input from the user and figures out what it means to the model.

@@ Line 5: / Line 5: @@
 = Model =
-* The model holds all data, state and application logic. The model is '''oblivious''' to the view and controller, although it provides an interface to manipulate and retrieve its state and can send notifications of state changes to observers. Typically a model would be represented in a POJO - combination of the business data and the methods that operate on that data.
+* The model holds all data, state and application logic. The model is '''oblivious''' to the view and controller, although it provides an interface to manipulate and retrieve its state and can send notifications of state changes to observers. Typically a model would be represented in a POJO - combination of the business data and the methods that operate on that data. It is the only part of the system that talks to the Database.
 = View =
-* Gives a representation of the model. The view usually gets the state and data it needs to display directly from the model.
+* Gives a representation of the model. The view usually gets the state and data of the model from the controller. (Controller puts the model data in a place where the view can find it).
 = Controller =
 * Takes the input from the user and figures out what it means to the model. E.g., a servlet normally operates in a controller role. Tells the model to update itself and then makes the new model state available to the view (e.g the JSP).

← Older revision		Revision as of 06:35, 9 June 2013
Line 13:		Line 13:
	= Controller =		= Controller =

−	* Takes the input from the user and figures out what it means to the model.	+	* Takes the input from the user and figures out what it means to the model. E.g., a servlet normally operates in a controller role. Tells the model to update itself and then makes the new model state available to the view (e.g the JSP).

@@ Line 1: / Line 1: @@
 = Intro =
-* The basic principle behind MVC is that the business logic is not only separate from the presentation, the business logic is not even aware of the presentation.
+* The basic principle behind MVC is that the business logic is not only separate from the presentation, the business logic is not even aware of the presentation. E.g, in a normal business app we can never assume that the business logic will only be invoked from the web and therefore should not place the business logic in say a servlet. It should be in a reusable Java class.
 = Model =

← Older revision		Revision as of 06:25, 9 June 2013
Line 1:		Line 1:
		+	= Intro =
		+
		+	* The basic principle behind MVC is that the business logic is not only separate from the presentation, the business logic is not even aware of the presentation.
		+
	= Model =		= Model =