On Wed, 17 Apr 2002 16:30:17 -0400, Smith, Kevin wrote: Hello Kevin,
I use it and it works like expected. As you already found out, it only works upon collections (I work with maps, so I had to build a wrapper for this). What is really done is replacing the collection with an instance of RelationCollection, which is indeed a proxy collection, which loads the objects as soon as they are first accessed. Even deletions and additions are handled without any implicited object loading. Where you have to take an eye on, is the class of the collection, which is given to you in the setXxxx-Routine of your BO. There you should see the RelationCollection.class. Hope that helps... >Can someone explain how lazy loading is supposed to work? I've set >lazy="true" on a couple of collections which could become quite large, but >I'm not seeing the expected behavior. > >By expected behavior, I mean that either a proxy object or just the identity >of each member in the collection is loaded. What I see in the collection is >the full-blown object. > >--Kevin > >-----Original Message----- >From: Gustavo Pistoia [mailto:[EMAIL PROTECTED]] >Sent: Wednesday, April 17, 2002 3:41 PM >To: [EMAIL PROTECTED] >Subject: Re: [castor-dev] Castor jdo limitation > > > >Hi. > I have read (somewhere) that lazy loading is only available for >collections. But can help in lotta cases. > >----------------------------------------------------------- >If you wish to unsubscribe from this mailing, send mail to >[EMAIL PROTECTED] with a subject of: > unsubscribe castor-dev > >----------------------------------------------------------- >If you wish to unsubscribe from this mailing, send mail to >[EMAIL PROTECTED] with a subject of: > unsubscribe castor-dev > > sincerely, Patric Bechtel IPCON Informationssysteme ----------------------------------------------------------- If you wish to unsubscribe from this mailing, send mail to [EMAIL PROTECTED] with a subject of: unsubscribe castor-dev
