Answer Posted / tarun tyagi

See if you are still writing applications that use
data-aware GUI components to interface directly with the
database, you might want to reconsider. Applications built
in this manner are not object oriented. Such two-layer
(GUI/Database) applications violate one of the primary
principles of object-oriented design: encapsulation.

Encapsulation is what allows a client to interact with an
object without knowledge of its implementation details, a
primary premise for loose coupling. In applications that use
data-aware widgets, the opposite is the case. The client and
the database are very tightly coupled. GUI code, business
logic, and SQL statements are all interwoven throughout the
application source code. As a result, the application can
become a maintenance nightmare. Any changes in the database
schema will surely cascade into unexpected failures.

Thats why we design a J2EE application so user data is
entered by way of a JSP page and managed by an underlying
Java Beans class

What is a war file?

1084

---

What function extracts specified characters from a string?

1002

---

describe method overloading

1017

---

Name the components that are termed to be Heavy-weight component but available in Light-weight components?

2491

---

What are the basic interfaces of java collections framework?

1119

---

Which java version is latest?

1031

---

What is synchronization and why is it important in java programming?

940

---

Explain the use of sublass in a java program?

1025

---

What is the destroy method?

1040

---

What is a conditional statement explain with example?

1016

---

What is the maximum size of byte array in java?

1011

---

State the main difference between c++ and java?

1088

---

What is java and its types?

1094

---

How does hashset work in java?

1120

---

What are constants and how to create constants in java?

986

---