Arkin wrote:
>
> It's possible that my bean will be doing something else in ejbLoad and
> ejbStore that is not affected by caching or is-modified, and any missing
> ejbLoad / ejbStore calls will break my bean.
>
> This is a consistent container - component contract that remains
> consistent regardless of any particular optimizations that CMP
> containers (but not BMP containers, and not all CMP containers in the
> same manner) may do.
If a vendor provides a vendor-specific element in the deployment descriptor
that enables the server to determine that ejbStore is not required, and you
willingly choose that option, you can benefit from an optimization as long
as you don't care that ejbStore isn't called. If you want it to be called,
you can't get the optimization (or you must use CMP where the CMP provider
can detect no changes and avoid the SQL update).
The spec is irrelevant in this respect. If you enable a proprietary optimization
and it doesn't hurt your bean behaviour. At worst your application's good
performance won't be portable, but all the other behaviour will be.
<vendor>
Sybase EAServer allow you to declare a method as Read Only (no code required).
If all accesses to a particular entity within a transaction are by Read Only
methods, we skip the ejbStore call.
</vendor>
________________________________________________________________________________
Evan Ireland Sybase EAServer Engineering [EMAIL PROTECTED]
Wellington, New Zealand +64 4 934-5856
===========================================================================
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".
