>This is due to the short transaction model. For the most time a client
>is not in a transaction at all. Only when they call a bean method do they
>start a transaction. During the time they were not inside a transaction,
>rows could have been updated and thus they can re-update those rows with
>stale data.
You are right, but is it not also true that ejbLoad will be called when
the first bean method is called? Thus the underlying row should be
write-locked at this point.
Floyd
===========================================================================
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".
