Imre wrote: > 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. > > This is fine insofar as the lazy instantation applies to the entity > objects. > The initial query referred to getting a list of read-only data items > from, > say, 1000 "database entities" without instantiating 1000 entity beans. > If we assume that more than the primary key has to be displayed, > what can we do with the EJBObject only invoke a business method to > get a description (which will instantiate). > > Is the preferred solution to have some independant (apart from sharing > the same persistent storage) read-only entity bean with a PK which > would be used to execute the query, and a method to construct the list > ? > (or does this even make sense ?) Or is the session bean/straight JDBC > approach better ? > > Might approaches be different for frequently required but fairly > static > entities (e.g. list product codes & names), vs dynamic/transactional > entities (e.g. list stock items for a product/location) ? > > Conor. =========================================================================== 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".
