<francais>
That's what I've been telling above, but for CMP-Bean, beacause it'd be
expensive for the container itself to check whether the bean state
changed.
</francais>
<vendor>
This is not the case. The Inprise Application Server 4.1 (IAS) performs this
and we have not seen any real performance issues, once caching of reflection
and other opimitizations are performed. With ejb 2.0 this is going to become
a lot easier to implement and allows for many other optimizations including
defered loading of some cmp fields. This all boils down to the same
concept/issue that has come up many times but in different guises. The view
of Inprise is that we should ** support ** developers by providing them with
non-intrusive and value added features i.e. there is no requirement for
having some persistence code mixed with business logic. Our cmp engine can
detect this change accurately for all beans where as each bean provider and
his beans is subject to the ** possibility ** of introducing code that
incorrectly produces the wrong result leading to either excessive writes or
worse no writes. Before responding please search the archives to find a
thread discussing this at length.
</vendor>
William Louth
Inprise
www.inprise.com/appserver
===========================================================================
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".
