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
Can we create an object of static class in java?
Is integer passed by reference in java?
What is assembly used for?
List some important characteristics on jre
How do you clear a method in java?
How to perform bubble sort in java?
What does it mean to be immutable?
Is ruby built on java?
What is the size of int?
What is math floor in java?
What is the synonym of string?
How many types of threads are there in java?
How many digits is int32?
Are arrays static in java?
What does serializing data mean?