Difference between container-managed & bean-managed
persistence?
Answers were Sorted based on User's Feedback
Answer / 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 |
Answer / john doe
In a CMP the task of mainitain the persitance is carried out
completely by the container. It is simpler for the developer
as the most of the tasks are handled by the contianer
itself. The developer does not have to worry about
connectivity or the JDBC
In a BMP the developer has to use database APIs to read or
write data into the DB. This gives him the flexibilty to
carry out the persistance operations which are too
complicated for the container to handle. He has to use EJB
QL (EJB Query Lanaguage) to interact with the database using BMP
Is This Answer Correct ? | 11 Yes | 4 No |
What is the difference between Session bean and Entity bean?one?
What is stateless and stateful?
What is the difference between @requestparam and @pathvariable?
What is backing bean?
Why stateless is better than stateful?
Enlist the CallBack methods of Session Bean?
What is ejb application?
How ejb invocation happens?
Is state maintained by a Stateless bean?
What is an ejb platform?
how can we decide a session bean as stateless or stateful without seeing jar file? i.e. by seeing the class file.
What are ejbs used for?