At 05:24 PM 1/12/99 -0500, you wrote:
>Hi,
>you can do this by simply including the bean in a transaction.
>According to the EJB specification, once a bean is included in a transaction
>no other thread can access it until the transaction commits or ends.
If you look at the different isolation levels and transactional status
you can achieve this sort of this, look at putting all the actions you
want into a session bean, that calls the entity bean for the operations
and having that session bean method use transaction level TX_REQUIRED
and isolation level TRANSACTION_SERIALIZABLE, then no other
will be able to access the session bean method and the changes won't
be committed until the end of the session bean method ...
--
Subvert the dominant paradigm
http://www.cyber4.org/members/grumpy/index.html
===========================================================================
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".
