Session Bean Component Contract,Stateless session beans: Stateless in stateless session beans signifies that an instance has no state for a specific client. However, the instance variables of the instance can contain the state across client-invoked method calls. A container only needs to retain the number of instances required to service the current client load. Due to client 'think-time', this number is typically much smaller than the number of active clients. Passivation is not needed for stateless session beans. The container creates another stateless session bean instance if one is needed to handle an increase in client work load. If a stateless session bean is not needed to handle the current client work load, the container and destroy it.
Daniel >From: Manish Syal <[EMAIL PROTECTED]> >Reply-To: [EMAIL PROTECTED] >To: [EMAIL PROTECTED] >Subject: Stateless session Bean >Date: Fri, 2 Nov 2001 13:09:49 +0530 > >Why does Stateless Session bean not store its state even though it has >ejbActivate and ejbPassivate ? What is the use of this ejbActivate and >ejbPassivate then? > >=========================================================================== >To unsubscribe, send email to [EMAIL PROTECTED] and include in the body >of the message "signoff EJB-INTEREST". For general help, send email to >[EMAIL PROTECTED] and include in the body of the message "help". > _________________________________________________________________ Get your FREE download of MSN Explorer at http://explorer.msn.com/intl.asp =========================================================================== To unsubscribe, send email to [EMAIL PROTECTED] and include in the body of the message "signoff EJB-INTEREST". For general help, send email to [EMAIL PROTECTED] and include in the body of the message "help".
