The client now has a handle to the EJBObject and can now invoke Bean-specific methods that are in turn delegated to the Bean itself. The Bean-specific methods are handled by the remote interface and the EJBObject. Entity Beans Unlike session Beans, entity Beans are optional in EJB 1.0. They will likely be required in EJB 2.0, yet many vendors plan on implementing entity Beans with their servers. An entity Bean is shared among multiple clients and represents specific data.
Entity Beans are transactional in nature and are persistent.
An entity Bean represents an underlying data object or context, such as a record in the database or a connection to an application. With entity Beans, the container maintains a pool of unused Bean instances. A primary key is used to uniquely identify an EJBObject. All EJBs will provide a primary key to their containers at the time they are created. It can also find a Bean by using application specific primary keys.