[hibernate-issues] [Hibernate-JIRA] Commented: (HHH-1435) many-to-one lazy seems to be broken in 3.1.x

[radhakrishna (JIRA)]

    [ http://opensource.atlassian.com/projects/hibernate/browse/HHH-1435?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=33631#action_33631 ] 

radhakrishna commented on HHH-1435:
-----------------------------------

What is going on? I cannot get the <many-to-one to load lazily when I use property-ref with Hibernate-Version: 3.2.4.sp1? 

"
Daniel Serodio added a comment - 20/Feb/06 12:46 PM

Besides the bug itself, I find the fact that the assertion was commented out a little preocupating. What is the purpose of the regression tests, if one comments out the a that shows that a bug has been introduced?
I've always considered the Hibernate QA process to be very trustworthy and thorough, but now I'm beginning to wonder if this is still true." :)

SOS
Krishna

> many-to-one lazy seems to be broken in 3.1.x
> --------------------------------------------
>
>                 Key: HHH-1435
>                 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-1435
>             Project: Hibernate Core
>          Issue Type: Bug
>          Components: core
>    Affects Versions: 3.1.2
>            Reporter: Frank Grimes
>            Assignee: Steve Ebersole
>            Priority: Critical
>             Fix For: 3.2.0.alpha2, 3.1.3
>
>
> When trying to upgrade from hibernate-3.0.5 to hibernate-3.1.1, my many-to-one lazy associations stopped working. (they're being fetched right away)
> I noticed that the test for that functionality in org.hibernate.test.instrument.InstrumentTest  was commented out at some point during 3.1 development.
> If I uncomment the assertion for the lazy loading of the many-to-one association, the test fails.
> The line in question is the following (line 160):
> //assertFalse(Hibernate.isPropertyInitialized(doc, "owner"));
> If this is/was a known issue, I didn't find any mention of it in either the forums or JIRA.
> It seems that both lazy="no-proxy" and lazy="proxy" fail on that test. (I tried modifying the mapping to see if maybe lazy="proxy" could be a possible migration path from the old lazy="true")
> Are there any plans to fix many-to-one lazy associations?
> FYI, I originally brought this issue up on the forums last week with no reply, hence the creation of this JIRA issue:
> http://forum.hibernate.org/viewtopic.php?t=954713
> Thanks.

-- 
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