Programming Tutorials

What do you understand by a container in J2EE?

By: Karthik in Interview Tutorials on 2012-06-16  

Normally, thin-client multi-tiered applications are hard to write because they involve many lines of intricate code to handle transaction and state management, multithreading, resource pooling, and other complex low-level details. The component-based and platform-independent J2EE architecture makes J2EE applications easy to write because business logic is organized into reusable components. In addition, the J2EE server provides underlying services in the form of a container for every component type. Because you do not have to develop these services yourself, you are free to concentrate on solving the business problem at hand.





Add Comment

* Required information
1000

Comments

No comments yet. Be the first!

Most Viewed Articles (in Interview )

Question: Difference between forward and sendRedirect in JSP?

Explain garbage collection?

What is Collection API?

Interview Question: What is the difference between Message Driven Beans and Stateless Session beans?

Differentiate between .ear, .jar and .war files.

Interview Question: What is re-entrant. Is session beans reentrant. Is entity beans reentrant?

What are all the different scope values for the tag?

The output of System.out.println(5>>2) in Java

What is the difference between interface and abstract class?

Interview Question: Write code of any Action Class?

What is similarities/difference between an Abstract class and Interface?

Is Iterator a Class or Interface? What is its use?

Interview Question: Do ActionForms have to be true JavaBeans?

What do you understand by a container in J2EE?

Question: How would you go about analyzing performance of an application?

Latest Articles (in Interview)