|
In container-managed persistence model, a container (deployment tool) generates the database access calls at the deployment time. This model requires the bean provider to specify the list of fields constituting the state of this bean in the deployment descriptor.
|
|
The container can produce the necessary data access calls for those fields (can do caching, connection pooling, etc).
|
|
This model de-couples the bean from its data access calls while it introduces a challenge to the container (deployment tool) developer to deal with the possible mapping problems between the fields and data source (no-free-lunch).
|
