[Hibernate-issues] [Hibernate-JIRA] Closed: (HB-395) Lazy Initialization used even when collection mapping says lazy="false"

[<leg...@at...>]

Message:

   The following issue has been closed.

   Resolver: Gavin King
       Date: Sat, 25 Oct 2003 5:06 PM

Thanks! Fixed.
---------------------------------------------------------------------
View the issue:

  http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HB-395


Here is an overview of the issue:
---------------------------------------------------------------------
        Key: HB-395
    Summary: Lazy Initialization used even when collection mapping says lazy="false"
       Type: Bug

     Status: Closed
   Priority: Blocker
 Resolution: FIXED

    Project: Hibernate2
 Components: 
             core
   Fix Fors:
             2.1 beta 5
   Versions:
             2.1 beta 3
             2.1 beta 4

   Assignee: 
   Reporter: Jason Carreira

    Created: Mon, 13 Oct 2003 4:46 PM
    Updated: Sat, 25 Oct 2003 5:06 PM
Environment: We use Oracle with WebLogic and WebSphere, but I've included a test case which fails as unit tests running against HSQL

Description:
If a child class has a Proxy (all the ones I've tested have themselves as the proxy class) and the parent class has a <set> mapping to the child class with lazy="false", then, if session.load(Parent.class, parentId) is called, then child collection will be lazily initialized. This doesn't happen with session.find(), for some reason. 


---------------------------------------------------------------------
JIRA INFORMATION:
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

If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira