18.04.2013 Views

B2B Integration : A Practical Guide to Collaborative E-commerce

B2B Integration : A Practical Guide to Collaborative E-commerce

B2B Integration : A Practical Guide to Collaborative E-commerce

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

Middleware Technologies 247<br />

EJB technology has gained wide spread industry adoption and support.<br />

The EJB specification is unique from CORBA and COM+ in that the<br />

specification was developed using industry-wide collaboration, as with<br />

CORBA, yet the specification is controlled by a single company, as<br />

with COM+. This has given EJB the advantage of obtaining industry<br />

acceptance from the application server vendors, while at the same time,<br />

the ability <strong>to</strong> advance and modify the specification quickly, since<br />

ultimately there is really only one owner and final decision-maker.<br />

At a high level, EJBs do not differ much from CORBA, or even<br />

COM+. EJBs require an IDL <strong>to</strong> separate the interface from implementation;<br />

it supports transaction management, component level security and<br />

messaging; and it is object-oriented based.<br />

EJB differs from its brethren, as follows:<br />

• EJB is a Java-based pro<strong>to</strong>col. Though EJBs can interface with non-<br />

Java components through wrappers or interfaces <strong>to</strong> CORBA, EJBs<br />

are Java at heart.<br />

• In addition <strong>to</strong> being platform independent, EJBs are also middleware<br />

independent. An EJB application can, in theory, be ported from one<br />

application server <strong>to</strong> another with minimal rework.<br />

• EJBs live in a container. The container provides several services for<br />

the EJBs, including lifecycle management and instance pooling and<br />

transaction management. The container intercedes between client<br />

calls on the remote interface and the corresponding methods in a<br />

bean <strong>to</strong> enforce transaction and security constraints. The container<br />

also enforces policies and restrictions on bean instances, such as<br />

reentrance rules and security policies.<br />

• EJBs were designed <strong>to</strong> wrap around, or encapsulate, existing legacy<br />

systems, applications and datas<strong>to</strong>res, allowing an organization <strong>to</strong><br />

leverage its existing infrastructure. These existing systems will appear<br />

as a standard bean within the container. EJB can also co-exist with<br />

other technologies, including COM/DCOM, ActiveX and CORBA.<br />

Types of beans<br />

The 'bean' part of Java Beans is Sun's name for a Java component.<br />

There are two types of enterprise beans: session beans and entity beans.

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!