>
> Because the entity object�s state accessed between the ejbLoad and ejbStore method
>pair is not
> protected by a transaction boundary for the methods that execute with an unspecified
>transaction con-text,
> the Bean Provider should not attempt to use the ejbLoad and ejbStore methods to
>control
> caching of the entity object�s state in the instance. Typically, the implementation
>of the ejbLoad and
> ejbStore methods should be a no-op (i.e. an empty method), and each business method
>should access
> the entity object�s state directly in the database.
If the implementation of non-transactional business method is expected to access the
entity object's state
directly from the database, then how is it supported for CMP entity beans ?
===========================================================================
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".
