Entity beans are transactional by nature. Session beans are not, however,
they can participate in transactions.
Take a look at these links:
Nuts and Bolts of Transaction Processing
http://theserverside.com/resources/nutsoftp.jsp
Pessimistic Vs. Optimistic Concurrency
http://theserverside.com/resources/news1.jsp#dev
"Understanding Transactions," describes the EJB architecture approach to
transaction demarcation.
http://developer.java.sun.com/developer/Books/ejbarch/trans.pdf
/kjetilhp
> -----Original Message-----
> From: Francesco Marchioni
> [mailto:[EMAIL PROTECTED]]
> Sent: 18. januar 2001 20:02
> To: [EMAIL PROTECTED]
> Subject: Can we say a final word about EJB cuncurrency ?
>
>
> Hello,
> I'm looking for some explanations about EJB and cuncurrency.
> Even if I have
> read
> many tutorials about EJB, I still don't have my mind clear.
>
> From what I have understood this is the situation about Entity Bean:
> Entity beans operates a bit like atomic operations. The same
> as when we
> update an "int" in Java is Thread-safe, also when one user
> attempts to do a
> "create", he's sure that
> the operation will be cuncurrent-safe because other Entity bean will
> synchronize with
> DB status when they want access to it.
>
> Is this true? And what is it very much different when we use
> Session Beans?
> Thanks a lot
> Francesco
>
> ==============================================================
> =============
> 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".
>
===========================================================================
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".
