Look harder. Not all Loader subclasses are in the loader package.
Robert Streich wrote:
I'm trying to sort out the way locks are handled. All the queries seem to dutifully run through Loader.applyLocks(), but none of the subclasses of Loader override the default implementation which just returns the string that was passed. Instead, all of the locking seems to be generated through EntityPersister.postInstantiate() where it creates a map of Loaders (SimpleEntityLoader) indexed by LockMode. Each Loader is created with an SQL string that already includes the lock. Then, when a lock is requested, it selects the Loader based on the LockMode that was requested.
Can someone clarify this?
thanks,
robert
-------------------------------------------------------
This SF.Net email is sponsored by BEA Weblogic Workshop
FREE Java Enterprise J2EE developer tools!
Get your free copy of BEA WebLogic Workshop 8.1 today.
http://ads.osdn.com/?ad_id=5047&alloc_id=10808&op=click
_______________________________________________
hibernate-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/hibernate-devel
------------------------------------------------------- This SF.Net email is sponsored by BEA Weblogic Workshop FREE Java Enterprise J2EE developer tools! Get your free copy of BEA WebLogic Workshop 8.1 today. http://ads.osdn.com/?ad_id=5047&alloc_id=10808&op=click _______________________________________________ hibernate-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/hibernate-devel
