Answer Posted / manish

MVC Architecture
It is just an application
interface. It has three parts.
1. Model
2. View
3. Controller
MVC was originally developed to map the traditional input,
processing, output roles into the GUI realm:
Input –> Processing –> Output
Controller –> Model –> View
The main aim of MVC architecture is to separate the
business logic and application data from the presentation
data to the user.
Architecture:

Model:
• A model is an object that manages information.
• It calculates, sorts, stores, retrieves, simulates,
emulates, converts, and does just about anything else you
can think of doing to information.
• The model by itself has no visual representation.
• It includes the validation rules.
• It does not know how to display the information it
contains.
• As MVC architecture the model information can be
divided into two categories:

i) Domain information Model
ii) Application information Model
I) Domain information Model:
• Domain information model includes that information
concerned with the problem domain.
• For example, if we have an airline reservation
application, then flight schedules, prices, seating
arrangements, and credit card numbers would all be domain
information.
II) Application information Model:
• Application information model is any information
that is used by the application but is not part of the
problem domain.
• In the airline reservation example, error messages
are part of the application information.
View:
• The view provides a visual representation of the
information contained in the model.
• As the information in the model changes, the view
should automatically change.
• A view depends on the information contained within
its model.
• Examples of views are input fields, text editors,
and even entire windows.
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.

View to model communication

The views know of the model and will interact
with the model.

• If a button is clicked an action
message might be sent to a model object in
order to get something done.

• If a new value is typed into an
entry field an update message might be sent to a model
object in order to give it its new value.

• If a value is needed for a display
an enquiry message might be sent to a model object in order
to get a value.


Model (and controller) to view communication

• Whenever some aspect of the model changes; an
aspect that is displayed in a view.
• Model and controller to communicate with view via
events.
• Using graphical components a list box, an entry
field or a radio button these view components will receive
event notifications such as needs contents, or clicked.
• The events will often come from the controller.
• Views register handlers for the events they wish to
handle.

What are best practices to follow while developing Struts2 application?

969

---

Why use spring, if you are already using struts?

936

---

Is Struts Framework part of J2EE?

972

---

Can explain about the validations and in your project where did u used the validations?

7487

---

What are the two different types of validations that the validator framework supports?

898

---

What is the purpose of @createifnull annotation annotation?

990

---

What is struts in java with example?

909

---

Can you explain aware interfaces in struts2?

976

---

How do u provide security to ur project?(Banking domain project)

4829

---

What are the classes used as part of struts framework ?

909

---

Which technologies can be used at view layer in struts?

1022

---

What are struts in java?

857

---

What are interceptors in struts 2?

965

---

Does Struts2 action and interceptors are thread safe?

1020

---

What is the design role played by struts?

961

---