[hibernate-issues] [Hibernate-JIRA] Commented: (HHH-1740) Build-time instrumentation breaks lazy="proxy"

[Steve Ebersole (JIRA)]

    [ http://opensource.atlassian.com/projects/hibernate/browse/HHH-1740?page=comments#action_23946 ] 

Steve Ebersole commented on HHH-1740:
-------------------------------------

1) Try not to take this the wrong way, but I could not care less whether or not *your* test case passes or fails.  Until it is part of the Hibernate test suite, it does not exist to me.
2) This is somehow caused by the threading of the junit tasks in conjunction with HSQLDB.  I test locally on Oracle and it works fine; but I did switch over to HSQLDB and it does indeed "lock up" there..

> 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
>     Assignee: Steve Ebersole
>     Priority: Critical
>      Fix For: 3.2.0.ga
>  Attachments: 312Document.class, Document.class, 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