> 1. Create your session bean right before you use it, in the doPost/doGet
> method of your servlet, or
This is fine.
> 2. Create an object pool of session beans during servlet initialization.
> The object pool would be an instance variable of your servlet and manage
the
> allocation/deallocation of beans to your web clients.
But there is no need to manage this object pool of beans. That's the
container's job.
> 2. One stateless session bean can be swapped to serve many clients,
whereas
> one stateful session bean ONLY serves ONE client.
Check the spec again (page 39)! A session bean (whether stateful or
stateless) is meant to serve one client.
Regards,
Subbu
===========================================================================
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".
