> How can the container ever select Option A? The container for example
> cannot determine whether the database is being accessed by another
> application or session bean for example.
The container can open a separate connection for the entity bean and
keep a long lived transaction on that connection, retaining the lock
permanently. All commits from other transactions will also perform a
commit within the entity bean's long-lived transaction.
I don't like it more than you do, but it's a nice option to have.
> Is this intended to be something settable in the deployment descriptor
> or is it left up to the container?
Seems to be up to the container to decide which option to select, what
locking to use, etc.
arkin
>
> dan
>
> ===========================================================================
> 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".
--
----------------------------------------------------------------------
Assaf Arkin www.exoffice.com
CTO, Exoffice Technologies, Inc. www.exolab.org
===========================================================================
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".
