EJB Tutorials

Types of EJB

There are three types of Enterprise Java Beans namely session beans, entity beans and message driven beans. This tutorial briefly explains these types of EJB.
Read More

Difference Between Session and Entity Beans

A session bean is an EJB that is created by a client and usually exists only for the duration of a single client-server session. A session bean usually performs operations such as calculations or database access on behalf of the client. While a session bean may be transactional, it is not recoverable if a system crash occurs. Session bean objects can be stateless or they can maintain a conversational state across methods and transactions. If a session bean maintains a state, the EJB container manages this state if the object must be removed from memory. However, persistent data must be managed by the session bean object itself.
Read More

Difference Between Stateful and Stateless Session Beans

Session beans can either be stateful or stateless. With stateful beans, the EJB container saves internal bean data during and in between method calls on the client’s behalf. With stateless beans, the clients may call any available instance of an instantiated bean for as long as the EJB container has the ability to pool stateless beans. This enables the number of instantiations of a bean to be reduced, thereby reducing required resources.
Read More

Required Classes/Interfaces That Must Be Provided for an Enterprise JavaBeans Component

Here we review the component architecture of EJBs. We also cover the required classes and interfaces for EJB, which include the home and remote interfaces, the XML deployment descriptor, the business logic (bean) class, and the context objects. While these names may or may not be meaningful to you at this point, you will soon understand how each of these pieces fits into the EJB component model.
Read More

Managing Security in EJB

To simplify the development process for the enterprise bean provider, the implementation of the security infrastructure is left to the EJB container provider and the task of defining security policies is left to the bean deployer. By avoiding putting hard-coded security policies inside bean code, EJB applications gain flexibility when configuring and reconfiguring security policies for complex enterprise applications. Applications also gain portability across different EJB servers that may use different security mechanisms.
Read More

Most Viewed Articles on EJB Difference Between Session and Entity Beans Difference Between Stateful and Stateless Session Beans Managing Security in EJB EJB 3 Entities Types of EJB EJB Entity Beans Required Classes/Interfaces That Must Be Provided for an Enterprise JavaBeans Component Web services basics

Latest Tutorials EJB : EJB 3 Entities EJB : Web services basics EJB : Required Classes/Interfaces That Must Be Provided for an Enterprise JavaBeans Component EJB : Difference Between Session and Entity Beans EJB : Difference Between Stateful and Stateless Session Beans EJB : Managing Security in EJB EJB : EJB Entity Beans EJB : Types of EJB