I think you are confusing bean instance with remote stub instance. The spec prohibits a container from accessing a bean instance from two threads. However, it is not as clear on client-side concurrent access to EJBObjects, and this behavior may be different across vendors. Note the spec is clear on concurrent access of StatefulSessionBean EJBObjects, which is prohibited and will throw ConcurrentModificationException or ReentranceException. When it comes to SLSBs, though, you're at the mercy of your container.
Gene
"Kenneth D. Litwak" <[EMAIL PROTECTED]> wrote:
According to the spec, it is illegal for two client threads to access the
same session bean instance. So let/'s say I get a handle to my bean instance
(not a home handle). I cannot give this handle to another client because it is
illegal for two clients to access the same session bean instance. I already
have a reference to the bean's EJBObject before I get a handle. So hat good is
the handle? Thanks.
Ken
===========================================================================
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".
Do You Yahoo!?
Yahoo! Autos - Get free new car price quotes
