Java Architectures - MVC1 AND MVC2

The objective of Java Architectures, especially Model View Controller or MVC architecture is to separate the business logic and application data from the presentation data to the user. 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 benefits like the separation of model and view allowing multiple views to use the same enterprise model, one can simply write a view and controller for it and wire them into the existing enterprise model, clarity of design which helps glancing at the model's public method list, making it easy to understand how to control the model's behavior. Efficient modularity allows any of the components to be swapped in and out as the user or programmer desires, ease of growth which helps controllers and views to grow as the model grows and easy distributability with the help of a few proxies.

The Model object in MVC is fully aware of all the data that are to be displayed. The model represents enterprise data and the business rules that govern access to and updates of this data. The view represents the presentation of the application. The view object refers to the model. It uses the query methods of the model to obtain the contents and renders it. It remains same if there is any modification in the business logic. Whenever the user sends a request for something then it always go through the controller. The controller is responsible for intercepting the requests from view and passes it to the model for the appropriate action.

Currently there are MVC1 architecture and MVC2 architecture. In MVC1, html or jsp files are generally used to code the presentation. To retrieve the data JavaBean can be used. In MVC1 architecture all the view, control elements are implemented using Servlets or Jsp. Also in MVC1 there is tight coupling between page and model as data access is usually done using Custom tag or through java bean call. The MVC2 architecture removes the page centric property of MVC1 architecture by separating Presentation, control logic and the application state.

In MVC2 architecture there is only one controller which receives all the request for the application and is responsible for taking appropriate action in response to each request. In MVC2 struts controller is there to control by using actionservlet, it reduce the lot of confusion. Using only one struts-config. xml one can configure all the flow of control. To summaries MVC is model which makes the application more flexible. Model, View and control is called as MVC.

Java Architectures like MVC 1 and MVC 2 are desirable in separating the business and application data from the presentation data. These two are vital tools in easy to use, easy to understand and easy to distribute design patterns. Java Architectures have played a stellar role in making life easy for the designers as well as the users.

What Java Development India Offer?

Java Development India offers Java Architecture MVC1and MVC2 consulting and Java Architecture MVC1and MVC2 related solutions from our offshore software development outsourcing centre at Kochi, Kerala in India.