From: Frank G. (JIRA) <no...@at...> - 2006-08-02 20:12:14
|
[ http://opensource.atlassian.com/projects/hibernate/browse/HHH-1740?page=comments#action_23824 ] Frank Grimes commented on HHH-1740: ----------------------------------- Scott, I tested using the junitinstrument target. I don't think that the junitsingle target calls the instrument target... so that might explain why you aren't getting the failure. In any case, I'll check it out from TRUNK to see if it might have been fixed. (perhaps by HHH-1931) Thanks. > Build-time instrumentation breaks lazy="proxy" > ---------------------------------------------- > > Key: HHH-1740 > URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-1740 > Project: Hibernate3 > Type: Bug > Components: core > Versions: 3.1.3, 3.2.0 cr1, 3.2.0.cr2 > Reporter: Frank Grimes > Priority: Critical > Attachments: HHH-1740.diff > > > I have a mapping that contains a many-to-one lazy="proxy". > This alone works fine: I see $$EnhancerByCGLIB$$ as the type when I do a load > Once I add a lazy property to the mapping and do build-time cglib enhancement, it breaks. > Not only is the lazy property listed in $CGLIB_READ_WRITE_CALLBACK, but also my lazy="proxy" association. (i.e. no more proxy object) > This works fine in hibernate-3.1.2. > This was originally brought up here: http://forums.hibernate.org/viewtopic.php?t=958881 > Please let me know if more info or a test case is needed. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://opensource.atlassian.com/projects/hibernate/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira |