Why would you desing a J2EE application so user data is
entered by way of a JSP page and managed by an underlying
Java Beans class?
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
| Is This Answer Correct ? | 10 Yes | 0 No |
Post New Answer View All Answers
Give example to differentiate between call by value and call by reference.
What is singleton class in ruby?
What is linked hashmap and its features?
Explain the features of java?
What do you understand by casting in java language?
What is the difference between @before and @beforeclass annotation?
What is java util?
What are the different access modifiers available in java?
Can we declare the static variables and methods in an abstract class?
What is derived datatype?
What is a instance variable in java?
If two threads have same priority which thread will be executed first ?
How can we use primitive data types as objects?
What are the advantages of java?
What does mean in regex?