Yes, basically but unfortunately if say a stored procedure or some
non-container managed process is also changing data in the table, this will
fail. From the feedback I hear in the field, setting db-is-shared for the
*whole* db is not realistic, many customers have something else going on but
more may be able to use a "table-is-shared" for a CMP entity since this
leaves their other tables free for non-container managed processes.
Otherwise we have to somehow take into account that external processes may
change the data, correct?

>
>It seems to me that you are basically describing optimistic locking at the
>container level, and yes, I agree, it is useful.
>
>--
>Cedric
>

_________________________________________________________________
Get your FREE download of MSN Explorer at http://explorer.msn.com

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