|
Problem |
What happens when an Enterprise JavaBeans (EJB) client no
longer needs a stateful session bean? |
|
Solution |
When an Enterprise JavaBeans (EJB) client no longer needs
a stateful session bean, the client explicitly removes it from the
container. By doing so, applications can decrease the need for
passivation, minimize container overhead, and provide an increased level
of performance.
If stateful session beans are not explicitly removed, resources are
consumed by the container that manages many stateful session beans. |
|
|
|
|
|
|