9.1.10 Commit options
The Entity Bean protocol is designed to give the Container the
flexibility to select the disposition of the instance state at
transaction commit time. This flexibility allows the Container to
optimally manage the caching of entity object�s state and the
association of an entity object identity with the enterprise bean
instances.
The Container can select from the following commit-time options:
� Option A: The Container caches a �ready� instance between
transactions. The Container
ensures that the instance has exclusive access to the state of the
object in the persistent storage.
Therefore, the Container does not have to synchronize the instance�s
state from the persistent
storage at the beginning of the next transaction.
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.
Is this intended to be something settable in the deployment descriptor
or is it left up to the container?
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".
