Difference between container-managed & bean-managed
persistence?
Answer Posted / janet
In container-managed persistence, entity bean data is
automatically maintained by the container using a mechanism
of its choosing. For example, a container implemented on top
of an RDBMS may manage persistence by storing each bean?s
data as a row in a table. Or, the container may use Java
programming language serialization for persistence. When a
bean chooses to have its persistence container managed, it
specifies which of its fields are to be retained.
In bean-managed persistence, the bean is entirely
responsible for storing and retrieving its instance data.
The EntityBean interface provides methods for the container
to notify an instance when it needs to store or retrieve its
data.
| Is This Answer Correct ? | 16 Yes | 1 No |
Post New Answer View All Answers
Enlist the contents of Container.
How can a CORBA object, accessed from a EJB?
What do you mean enterprise javabeans (ejb) container?
How can a session bean be configured for transactions of bean-managed?
Why do we need ejb?
What changes have been made in ejb 2.0 specifications?
What do you mean by re-entrant? Can you say that session beans as re-entrant? Can entity beans be specified as re-entrant?
What is the procedure of ejb container to handle exceptions?
How to find ejb version in websphere?
Why do we use ejb?
What is difference between ejb 1.1 and ejb 2.0?
What are the callback annotations for the stateless bean?
What optimization could I use if the ejb container is the only point of write access to the database?
What is ejb and how it works?
What are the system services of ejb container?