Advertisement
Home arrow Java Articles arrow J2EE EJB arrow Introduction to Java Enterprise Edition [ Tutorial ]
Introduction to Java Enterprise Edition [ Tutorial ] E-mail
Written by sunil boricha   
Article Index
Introduction to Java Enterprise Edition [ Tutorial ]
Part-2 Multi-tiered Architecture
Part-3 Java Enterprise Edition API
Part-4 Enterprise Java Beans

This tutorial provides an overview of Java Enterprise Edition. It helps understand Multi-tired Architecture, J2EE API and types of Enterprise Java Beans.
Learning Objectives:

After completing this tutorial, you will be able to:
  •  Understand Multi-tired Architecture
  •  Know about J2EE API
  •  Understand about types of EJBs

related links



Introduction

J2EE stands for Java 2 Enterprise Edition. It is a specification provided by Sun Microsystems for server side development in Java that is deployable in distributed environments.

One unified specification of J2EE has helped to create applications that are vendor independent. There are several application servers currently available in the market on which a server side Java application can run. IBM Websphere, BEA Weblogic, Sun Java System Application Server, Oracle 9i etc are most common examples. All these servers are J2EE compliant servers as the vendors for these servers (IBM, BEA, Sun, Oracle) have made the servers as J2EE compatible. Due to this, an application developed with J2EE compliance ad running on one server can run on another server that supports J2EE, without any change (at least in theory).

J2EE also facilitates component-based development. It gives different technologies to develop the components at different layers. A JSP (Java Server Pages) developer can create the web pages. A business component developer can create EJBs. An application server vendor can create a J2EE engine that takes cares of factors like performance, transaction, multithreading etc. Each of these roles can execute their job without being concerned about how the other role has implemented its component. For example, a JSP developer need not know how an EJB developer is retrieving data and processing it. Similarly an EJB developer need not know how the JSP developer is going to display the data or how the application server vendor is managing the integrity of the transaction of the EJBs that he created.





 

Sponsored

Login / Logout


//SPONSORED
© 2004-2009 Anil Kumar Kuchana SkillFox.com