Hey
Evan Ireland wrote:
> One way we handle this is to allow the same object reference for a stateless
> object to be used simultaneously by multiple client threads. That doesn't
> mean that the same bean instance is used concurrently, in fact each
> concurrent call through the same object reference is serviced by a separate
> bean instance.
This I can understand.
> If the session bean is not stateless, then the servlet engine will allow the
> creation of a pool of servlet instances, each of which is used for only one
> client at a time.
This I don't understand. The session, where the handle to the stateful
session bean is kept, is shared between all servlet instances, so this
does not prevent two servlets from concurrently calling the session
bean. Pleasy clarify/expand your solution.
/Rickard
--
Rickard �berg
@home: +46 13 177937
Email: [EMAIL PROTECTED]
http://www.dreambean.com
Question reality
===========================================================================
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".
