A question for the experts:

I am using the ODMG API (RC4) with setting ImplicitLocking=false in 
OJB.properties.

When I obtain a READ lock on an object that has proxy references, all 
proxies are getting materialized. Due to above setting, there are no READ 
locks put on the referenced objects, so I wonder why this happens. 

Stepping through the code shows, that this happens in the method 
assertFkAssignment in class TransactionImpl. This method gets called from 
assignReferenceFKs, which in turn gets called from the lock method.

Is this really necessary at this point? Is there a way to avoid this? It 
seems to me that this makes the proxy feature almost useless for ODMG, and 
in my case materializing all references would be prohibitively expensive. 

Gerhard

Reply via email to