| 1 |
When container-managed persistence is in use, there are some changes since the generated objects also implements the creation, removal, and look up of the entity in the underlying database.
|
| 2 |
First, the fields of bean class is described in the deployment descriptor with cmp-field tags so that the container can figure out the entity fields to prepare necessary data access protocol calls.
|
| 3 |
Second, the semantic of ejbCreate(), ejbRemove(), ejbLoad(), and ejbStore() methods changes since the bean is no longer responsible for synchronization of its state with the data store. Also, the implementation of finder methods are provided by the container since the bean class is de-coupled from the data store.
|
