Floyd,
What you are suggesting is covered in the EJB spec in section 9.1.10, and it
is referred to as Commit Option A.
"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."
I haven't run across an EJB server that does not support Option A yet. Are
there any?
jim
> Floyd Marinescu wrote:
> > Hi everyone,
> >
> > Most appservers re-load your entity bean before each transaction
call,
> > to ensure consistency with the database. However, if you can ensure that
the
> > database won't be changed by anyone except your app. server, these
numerous
> > and expensive load calls should be avoided. A bean should only be loaded
> > when it is activated (associated with a particular instance).
===========================================================================
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".
