A design pattern describes a proven solution to a recurring design problem, placing particular emphasis on the context and forces surrounding the problem, and the consequences and impact of the solution.
There are many good reasons to use design patterns. Here are three:
1) They are proven. You tap the experience, knowledge and insights of developers who have used these patterns successfully in their own work.
2) They are reusable. When a problem recurs, you don't have to invent a new solution; you follow the pattern and adapt it as necessary.
3) They are expressive. Design patterns provide a common vocabulary of solutions, which you can use to express larger solutions succinctly.
The goal of the MVC design pattern is to separate the application object (model) from the way it is represented to the user (view) from the way in which the user controls it (controller).
The MVC architecture has the following benefits:
1) Multiple views using the same model: The separation of model and view allows multiple views to use the same enterprise model. Consequently, an enterprise application's model components are easier to implement, test, and maintain, since all access to the model goes through these components.
2) Easier support for new types of clients: To support a new type of client, you simply write a view and controller for it and wire them into the existing enterprise model.
3) Clarity of design: By glancing at the model's public method list, it should be easy to understand how to control the model's behavior. When designing the application, this trait makes the entire program easier to implement and maintain.
4) Efficient modularity: of the design allows any of the components to be swapped in and out as the user or programmer desires - even the model! Changes to one aspect of the program aren't coupled to other aspects, eliminating many nasty debugging situations. Also, development of the various components can progress in parallel, once the interface between the components is clearly defined.
5) Ease of growth: Controllers and views can grow as the model grows; and older versions of the views and controllers can still be used as long as a common interface is maintained.
6) Distributable: With a couple of proxies one can easily distribute any MVC application by only altering the startup method of the application.
MVC is an approach for developing interactive applications ie it results in events through user interaction.MVC stands for Model View Controller.Model is responsible for holding the application state view is for displaying the current model and controller handles the events.
A design pattern describes a proven solution to a recurring design problem placing particular emphasis on the context and forces surrounding the problem and the consequences and impact of the solution.
There are many good reasons to use design patterns. Here are three:
1) They are proven. You tap the experience knowledge and insights of developers who have used these patterns successfully in their own work.
2) They are reusable. When a problem recurs you don't have to invent a new solution; you follow the pattern and adapt it as necessary.
3) They are expressive. Design patterns provide a common vocabulary of solutions which you can use to express larger solutions succinctly.
The goal of the MVC design pattern is to separate the application object (model) from the way it is represented to the user (view) from the way in which the user controls it (controller).
The MVC architecture has the following benefits:
1) Multiple views using the same model: The separation of model and view allows multiple views to use the same enterprise model. Consequently an enterprise application's model components are easier to implement test and maintain since all access to the model goes through these components.
2) Easier support for new types of clients: To support a new type of client you simply write a view and controller for it and wire them into the existing enterprise model.
3) Clarity of design: By glancing at the model's public method list it should be easy to understand how to control the model's behavior. When designing the application this trait makes the entire program easier to implement and maintain.
4) Efficient modularity: of the design allows any of the components to be swapped in and out as the user or programmer desires - even the model! Changes to one aspect of the program aren't coupled to other aspects eliminating many nasty debugging situations. Also development of the various components can progress in parallel once the interface between the components is clearly defined.
5) Ease of growth: Controllers and views can grow as the model grows; and older versions of the views and controllers can still be used as long as a common interface is maintained.
6) Distributable: With a couple of proxies one can easily distribute any MVC application by only altering the startup method of the application.
MVC architecture gives the simplest way for the developing an application using J2ee technologies.In this model is where we can develop our bussiness logic and view where we can develop our presentation logic that means if you are going to use the structs framework here the model is nothing but an EJB object r it may be a model class object and view is JSP pages or servlets where u r goin to implements ur presentation logic and finaaly the controller is Action servlet in struts which is indirectly controlling the whole process.Likewise by dividing our project development we can achive highly flexible and efficient application.
i have completed my BTech three years back in Electrical and electronic. Now iam learning core jave to become programer in java. i want job as software programer will you plz help me.
- In the MVC design pattern application flow is mediated by a central Controller. The Controller delegates requests to an appropriate handler. The handlers are tied to a Model and each handler acts as an adapter between the request and the Model. The Model represents or encapsulates an application s business logic or state. Control is usually then forwarded back through the Controller to the appropriate View. The forwarding can be determined by consulting a set of mappings usually loaded from a database or configuration file. This provides a loose coupling between the View and Model which can make an application significantly easier to create and maintain. Controller: Servlet controller which supplied by Struts itself; View: what you can see on the screen a JSP page and presentation components; Model: System state and a business logic JavaBeans.
hello this is rahul.i can tell u one thing as ur frm other stream and hving three years gap better to learn J2EE and put some fake experience in tht .so tht u can easily find a job.if ur in hyd it is better to go for coaching for J2EE as in hyd there r few institues with good coaching centersok all the bestbut its difficult to find a job in corejavaokgood luck byeAsha Wrote: i have completed my BTech three years back in Electrical and electronic. Now iam learning core jave to become programer in java. i want job as software programer will you plz help me.
3 
0