As I understand it, according to the spec, an entity bean can be shared
concurrently by multiple callers, though the container is free to implement
however it wishes. When multiple callers use the same primary key to access a
bean, which I think generally results in the same EJBObject being used by all
callers to get to one entity bean instance, is there ever a time in which,
rather than all the clients waiting their turn (assuming a transaction
isolat8ioon requiring exclusive locking) the container would refuse the caller
and send back an error message becasuse the bean (and the row implicitly) is in
use and the row or object is locked? 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".
