particular scenario where lazy-loading is used in conjunction with
long-duration transactions without a performance cache.
First I load object A in one transaction the push it out somewhere in
another tier. The object is later modified and then passed back to the
server for an update. How does Castor distinguish between fields that are
null because they haven't been loaded vs. fields that are null because they
may have been cleared?
-----------------------------------------------------------
If you wish to unsubscribe from this mailing, send mail to
[EMAIL PROTECTED] with a subject of:
unsubscribe castor-dev
This message was posted using eunum
To interact with a real-time, threaded interface to this e-mail list, clickthe link below:
[EMAIL PROTECTED]
