[
http://opensource.atlassian.com/projects/hibernate/browse/HHH-1740?page=c...
]
Frank Grimes commented on HHH-1740:
-----------------------------------
The ant changes made the failure more deterministic.... when run individually, the
javassist and cglib instrument tests run fine.
When run together as part of the main test suite, org.hsqldb.persist.NIOLockFile errors
occur on the second one that is run.
Switching HSQLDB to in-memory mode (in hibernate.properties) gets rid of the error.
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,
Hibernate3-Branch_3_2.diff, TestLazyManyToOne-Branch_3_2.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....
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira