This week's book giveaway is in the OO, Patterns, UML and Refactoring forum. We're giving away four copies of Refactoring for Software Design Smells: Managing Technical Debt and have Girish Suryanarayana, Ganesh Samarthyam & Tushar Sharma on-line! See this thread for details.
I need clear explanation of mvc design pattern. What i read in google is " controller: which is responsible for
access the client request and process the request then send response back to client. view : means presentation
logic normally html and jsp. Model is manipulate data. which means which contains code to store and retrieve
data from database or any thing else. Need clear usage of model in mvc pattern
I don't know what I can say that will make it more clear: the model is whatever you're doing stuff to: a user, a library book, and so on. Note that the Struts version of MVC is a somewhat weaker version of what *real* MVC is: in the web world most people view the model as just that--a DTO. In a real MVC app, like the article says, the model can tell views it has changed, and so on.
The Model application in a Model-View-Controller implementation executes business logic. It does not execute presentation logic which is part of the View. And it does not execute Controller logic which is in the Controller.
The Model application consists of business objects AND the logic that executes with these objects (aka business logic.)