UNIT 2 ENTERPRISE JAVA BEANS: ARCHITECTURE AND GOALS

UNIT 2 ENTERPRISE JAVA BEANS: ARCHITECTURE AND GOALS

The EJB Specifications try to meet several goals which are described as following:
 

• EJB is designed to make it easy for developers to create applications, freeing them
from low-level system details of managing transactions, threads, load balancing,
and so on. Application developers can concentrate on business logic and leave the
details of managing the data processing to the framework. For specialised
applications, though, it's to customise these lower-level services.
 

• The EJB Specifications define the major structures of the EJB framework, and then
specifically define the contracts between them. The responsibilities of the client, the
server, and the individual components are all clearly spelled out. A developer
creating an Enterprise JavaBean component has a very different role from someone
creating an EJB-compliant server, and the specification describes the
responsibilities of each.
 

• EJB aims to be the standard way for client/server applications to be built in the Java
language. Just as the original JavaBeans (or Delphi component etc.) from different
vendors can be combined to produce a custom client, EJB server components from
different vendors can be combined to produce a custom server. EJB components,
being Java classes, will of course run in any EJB-compliant server without
recompilation. This is a benefit that platform-specific solutions cannot offer.
 

• Finally, the EJB is compatible with and uses other Java APIs, can interoperate with
non-Java applications, and is compatible with CORBA