<snip>
>
> > 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.
>
Not exactly true. Some of the Application Servers do not support Instance
pooling at the server end and thus, encourage pooling of stateless session
bean handles at the client end. In such cases many instances of the servlet
will pick the reference off the pool to service the request and return it
back and thereby one stateless bean can serve many clients.
Best if you can store the bean handles in the HttpSession object at the
servlet, or else do the lookup in the init method and do the create/business
method in the doPost/doGet and rely on the App Server to instance pool the
beans if it supports it.
-- Aravind
===========================================================================
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".
