>as if one transaction ran, then the other - it's "serialized"). If the
>first txn tries to update data the second transaction updated, then it gets
>rolled back.
Hi Micheal, thanks for the comments. One question I have then is how does
the ejbCode catch the transaction rollback and notify the client? That is,
if in your session bean code you update some entity beans, as far as I know,
they won't be committed until the entire transaction is over (the session
bean crosses the end of its "method"), and control allready returned to the
client. If this is so, where can we place exception handling code to catch
transaction collisions?
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".
