Answer Posted / rk

I do not see a single correct answer.

In Struts1, Action resources must be thread-safe or
synchronized. So Actions are singletons and thread-safe,
there should only be one instance of a class to handle all
requests for that Action. The singleton strategy places
restrictions on what can be done with Struts1 Actions and
requires extra care to develop.

However in case of Struts 2, Action objects are instantiated
for each request, so there are no thread-safety issues. (In
practice, servlet containers generate many throw-away
objects per request, and one more object does not impose a
performance penalty or impact garbage collection.)

reference:
http://www.javabeat.net/qna/690-struts-1x-vs-struts-20/

How struts control data flow?

1100

---

Explain about tiles?

1039

---

Can you give an overview of how a struts application flows?

950

---

What is role of action class?

1048

---

What is struts in j2ee?

934

---

What is the purpose of @result annotation?

1143

---

What is the default location of result pages and how can we change it?

1003

---

What is xml based validation in struts2?

1063

---

How do you find the struts version being used in a project?

942

---

How does one create an action in struts 2?

949

---

For a single Struts application, can we have multiple struts-config.xml files?

978

---

Is struts efficient?

922

---

What is the purpose of interceptors?

1001

---

Is struts compatible with other java technologies?

954

---

What are the 5 constants of action interface?

1011

---