Hi Kevin, > > Hello All, little question about ODMG Transaction object lock > > > In the transaction lock feature the collection references are > locked in > the method lockCollection(...), but if when have a collectionProxy > implementation, the collection will be retrieved right now. > > So the proxy attribute is useless with ODMG transaction because on > whenever u lock an object the proxyCollection will be retrieved and > loose the fantastic feature of lazy loading >
works as designed :-( > Are we forced to lock a collection which is a collectionProxy if the > collections wasn't retrieved before? Simply because objects in the > collection has not been updated ... It may sound strange but this is intended! Here is why: The collection represented by the proxy might contain an object X. If we do not load the proxy concurring transactions will never know that X is (implicitely) locked by the current transaction. But there is a way out: You can set ImplicitLocking=false in OJB.properties. This will disable implicit (and recursive) locking. Of course the user is responsible for proper explicit locking if implicit locking is disabled! cheers, Thomas > > Please answer this mail, because the lazy loading feature for me and > loose it with ODMG is not very cool !!! > -- > Kevin Viet <[EMAIL PROTECTED]> > ActiVia Networks > > > > > -- > To unsubscribe, e-mail: > <mailto:[EMAIL PROTECTED]> > For additional commands, e-mail: > <mailto:[EMAIL PROTECTED]> > >
Mahler Thomas.vcf
Description: Binary data
-- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
