The purpose of Stateful session bean is to serve the client,i.e maintain a history of Client's wish list, right when the client enters the application,it cannot drop off in the middle (unless the server goes down).
So,resources can be accessed by the bean because he(client) is initiating the process of bean creation(i.e.. HE wants to interact with the app,a state for himself), which again based on the business logic will trigger call to resource mgrs and other beans.
So its because the creation is triggered by the client,(again impl dependent), we give him "exclusively made for U" bean.
Where as in case of stateless session bean we are leaving creation at the container's will n wish, so that bean doesn't hang around with connection to resource mgr open and gossipping around with other beans in the pool.
Correct me if i'm wrong.....
![]()
happened...
is it that since the EJBObject is implemented by the container, it doesn't matter how the container wishes, activation is done.(i mean Is the code that container calls activation on an instance,part of EJBObject interface implementation).
?