But at the end of the day, when Daniel is populating his list of 1000 found items for the user to choose from, I'm assuming he still needs to invoke a method on each and every found EJB object to get, e.g. a Description -- which would still cause an EJB object activation/instantiation/or whatever ? One could have a separate EJBean which just manages retrieval of these display properties with mapping to a PK (e.g. a Session bean which others have suggested). But if you only want to use the finder methods and need some info from each bean to display, I can't see how you get around some sort of bean-by-bean activation (even if the container is smart enough to do "lightweight" activations). - Eric Yu > -----Original Message----- > From: A mailing list for Enterprise JavaBeans development > [mailto:[EMAIL PROTECTED]]On Behalf Of Imre Kifor > Sent: Tuesday, May 11, 1999 10:13 AM > To: [EMAIL PROTECTED] > Subject: Re: Is something missing in the actual EJB > SPECS?Willthenextversion solve this? > > > Daniel, > > >In spec 1.1, we can read at 9.3.2 p135 > > > > ... > >If the ejbFind<METHOD> method returns a collection of > primary keys, the > >implementation of the find<METHOD>(...) method must create a > collection of > EJB > >objects for the primary keys, and return the collection to > the client. > > > It is not required that all objects be created when the collection is > returned. The idea behind collection iterators is that they allow lazy > creation of element references. > > Imre Kifor > Valto Systems > =========================================================================== To unsubscribe, send email to [EMAIL PROTECTED] and include in the body of the message "signoff EJB-INTEREST". For general help, send email to [EMAIL PROTECTED] and include in the body of the message "help".
