Golgappa.net | Golgappa.org | BagIndia.net | BodyIndia.Com | CabIndia.net | CarsBikes.net | CarsBikes.org | CashIndia.net | ConsumerIndia.net | CookingIndia.net | DataIndia.net | DealIndia.net | EmailIndia.net | FirstTablet.com | FirstTourist.com | ForsaleIndia.net | IndiaBody.Com | IndiaCab.net | IndiaCash.net | IndiaModel.net | KidForum.net | OfficeIndia.net | PaysIndia.com | RestaurantIndia.net | RestaurantsIndia.net | SaleForum.net | SellForum.net | SoldIndia.com | StarIndia.net | TomatoCab.com | TomatoCabs.com | TownIndia.com
Interested to Buy Any Domain ? << Click Here >> for more details...


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?

Answers were Sorted based on User's Feedback



Why would you desing a J2EE application so user data is entered by way of a JSP page and managed b..

Answer / 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

Why would you desing a J2EE application so user data is entered by way of a JSP page and managed b..

Answer / nash

Its always better to seggregate/seperate the duties of
components. Its correct way to implement MVC architecture.

JSP takes care of View Component and Bean Object will be
used as Transfer Object in application.

Is This Answer Correct ?    7 Yes 1 No

Why would you desing a J2EE application so user data is entered by way of a JSP page and managed b..

Answer / sandeep

you can use mvc1 to implement the such requirement.

Is This Answer Correct ?    9 Yes 4 No

Why would you desing a J2EE application so user data is entered by way of a JSP page and managed b..

Answer / jana

i dnt knw

Is This Answer Correct ?    1 Yes 1 No

Why would you desing a J2EE application so user data is entered by way of a JSP page and managed b..

Answer / rajesh

As per my understanding, Java Bean exposes the properties
of the JSP page in a consistent way.

Also it represents the jsp page as a simple java object
(POJO) which is having certain state. and it is easy to
handle java beans.

Is This Answer Correct ?    0 Yes 4 No

Post New Answer

More Core Java Interview Questions

How to print nodes of a Binary tree?

0 Answers  


What does t in java mean?

0 Answers  


Why we used vector class?

0 Answers  


what are the design patterns in struts?

1 Answers  


What do you mean by jjs in java8?

0 Answers  


what are ER diagrams?

2 Answers  


Can a static method be final?

0 Answers  


Which is not Object in Java?

10 Answers   Honeywell,


Is upper case in java?

0 Answers  


What is a variable simple definition?

0 Answers  


Why do we need autoboxing in java?

0 Answers  


Explain scope or life time of local variables in java?

0 Answers  


Categories