-
Note: A key to understanding much of EJB is that the bean implementation is
never referred to directly by the client
-
As we'll see later this allows the implementation of container managed
transactions, persistence, and security
-
It also allows various performance optimizations to be made
-
It implies that the lifetime of bean implementation object and the lifetime of
the bean reference that a client has are decoupled
-
As can be seen from the lifecycle
diagram, An entity bean implementation exists in one of 3 states
-
Non-existent
-
Pooled
-
Ready
|