Thus, EJB does indeed support the effect of pooling stateful session beans.
EJB containers exploit this very paradigm
these were the words from mastering ejb book.
also these were there..
But this pooling effect does not come for free�the passivation/activation steps could entail an input/output bottleneck.
so ejb spec does not mandate this requirement.so it depends on the vendor.
also for stateful session beans in transaction this discussion is not applicable at all.
so you can think of there is no pool for stateful beans(it would be easy that way to distinguish many points with stateless).
you cannot keep creating new beans for every user.
creating stateful beans are much cheaper than passivating and activating them. also if all the clients to stateful beans are active then passivating them to create a new bean is a worst idea.
are the contents of the bean passivated ?
contents are passivated.
Sorry for the extremly long question.
Sorry for the extremly long answer.
[ September 01, 2006: Message edited by: cheenu Dev ]