Hi All,

After upgrading from hibernate-3.1.2 to hibernate-3.2.0.cr1, I hit some problems with lazy loading that I have been trying to track down.

One big difference I have noticed in my debugging that looks fishy is the following:

I have mappings that contain both lazy properties, and lazy many-to-one proxy associations.
In 3.2.0.cr1, all lazy properties *and* lazy many-to-one proxy associations are listed as uninitialized fields in the $CGLIB_READ_WRITE_CALLBACK FieldInterceptorImpl.
This occurs whether many-to-one lazy="proxy" is set explicitly or implicitly (from default), but does not occur when lazy="false" is specified.

In 3.1.2, (as I would expect) only the properties that I have specified as lazy in the mapping file show up as uninitialized fields in the $CGLIB_READ_WRITE_CALLBACK FieldInterceptorImpl, and not the many-to-one associations.

I would expect that only lazy="no-proxy" associations and lazy properties would be affected by the build-time instrumentation.
Is this correct?
If so, please let me know if a JIRA and test case are necessary.

Thanks!

Upon further inspection, I believe that this may in fact be related to http://opensource.atlassian.com/projects/hibernate/browse/HHH-1610.

Just to simplify my question a bit... should lazy="proxy" associations be showing up in $CGLIB_READ_WRITE_CALLBACK's uninitialized fields?