Moreover, a client can later connect to the same entity bean using its object reference because it encapsulates a unique primary key allowing the enterprise bean or its container to reload its state. Entity beans can thus survive system shutdowns. Because it is container-managed, the implementation is independent of the data source. All container-managed fields need to be specified in the deployment descriptor, however, for the persistence to be automatically handled by the container. Consequently, this implementation is less adaptable than the previous one as the persistence needs to be hard-coded into the bean.
Entity beans can participate in transactions.
Entity beans represent data in a domain model. Entity beans are persistent. They live as long as the data lives in the domain model. Entity beans can survive EJB server crashes. Any EJB server crash is always transparent to the client.