Hi,
There is little debate going on between me and my friend
,like when Container call Passivate method.
I say " IT"S container algorithm....."after reading following lines from
EJB SPEC 2.0 (Page no 78)
Quote
**************
The container’s caching algorithm may decide that the bean instance should be evicted from memory (this could be done at the end of each method, or by using an LRU policy). The container issues ejbPassivate on the instance
***************
But my friend says "Whenever container wants to increase the size of pool,it calls passivate method..he came to this conclusion after reading
below from EJB2.0(page no 70)
Quote
***************
To efficiently manage the size of its working set, a session bean container may need to temporarily
transfer the state of an idle stateful session bean instance to some form of secondary storage. The transfer
from the working set to secondary storage is called instance passivation. The transfer back is called
activation
****************
Can anyone put more light on this...
James