> From: A mailing list for Enterprise JavaBeans development
> [mailto:[EMAIL PROTECTED]]On Behalf Of Peter Verkest

> Optimistic locking at the container would be great indeed, but
> how about optimistic locking at the DB level?

Most of the databases already offer this (starting with Oracle).  It's the
easiest option for an EJB container provider, we have almost nothing to do
:-)

> If we are working in a cluster with n nodes, is there any need to
> ejbLoad an entity more than once per transaction then?

No, but in the case of optimistic concurrency at the container level, a
check will be needed when the transaction commits to make sure the UPDATE
won't overwrite data written externally since the transaction was begun.

--
Cedric

===========================================================================
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".

Reply via email to