What is Struts - Struts Architecture
Struts is an open source framework used for developing J2EE web applications using
Model View Controller (MVC) design pattern. It uses and extends the Java Servlet API
to encourage developers to adopt an MVC architecture. Struts framework provides
three key components:
1. A request handler provided by the application developer that is used to
mapped to a particular URI.
2. A response handler which is used to transfer the control to another resource
which will be responsible for completing the response.
3. A tag library which helps developers to create the interactive form based
applications with server pages.
Struts provides you the basic infrastructure infrastructure for implementing MVC
allowing the developers to concentrate on the business logic.
MVC Architecture
The main aim of the MVC architecture is to separate the business logic and
application data from the presentation data to the user.
Here are the reasons why we should use the MVC design pattern.
1. They are reusable : When the problems recurs, there is no need to invent a
new solution, we just have to follow the pattern and adapt it as necessary.
2. They are expressive: By using the MVC design pattern our application becomes
more expressive.
1). Model: The model object knows about all the data that need to be displayed. It is
model who is aware about all the operations that can be applied to transform that
object. It only represents the data of an application. The model represents enterprise
data and the business rules that govern access to and updates of this data. Model is
not aware about the presentation data and how that data will be displayed to the
browser.
2). View : 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. The view is not dependent on the application logic. It remains same if
there is any modification in the business logic. In other words, we can say that it is
the responsibility of the of the view's to maintain the consistency in its presentation
when the model changes.
3). Controller: 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. After the action has been
taken on the data, the controller is responsible for directing the appropriate view to
the user. In GUIs, the views and the controllers often work very closely together.
docsity.com
