Depending on your requirements choose an appropriate isolation level for
the bean. Some application servers choose,by default,
TRANSACTION_SERIALIZABLE as the isolation level.
This is the strictest isolation level and ensures all the ACID properties
and guarantees fully independent transactions. Therefore, even if
transactions occur concurrently, users will view their effects only
successively. However, database access performance may suffer when this
isolation level is used.
G.Vijay
hi
we are developing a standard alone application with EJB in the middle tier
and Swing in the front end.And we are using
completely BMP entity for accessing our data.
The case is like this
I have client A and client B
my client A calls my ejbLoad() and gets all the record 1 in the form and
started modifying and in the mean time
my client B also calls the ejbLoad() for the record 1 and started modifying
the record.
I don't have any issues when the first client or in that matter who ever
updates first .
but when the second client tries to update after the first one , what will
happen to my data integrity?
and what about ACID properties ?
Can some one kindly let me know whether these kind of issues will be taken
care by container or not?
Thanks in advance
Saminathan.
===========================================================================
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".
