If your situation is CMP/CMR and the code mentioned is using local
interfaces directely, the container can be fine-tuned using pre-defined load
groups and paging. This way you can even iterate a GIANT collection with
cost only to memory within the AS.
Cheers,
Marco Garbelini
----- Original Message -----
From: "Dies Koper" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Friday, May 30, 2003 5:49 AM
Subject: [Fwd: Re: EJB container - does it able to read ahead?]
> Hello Kirril,
>
> Your first line consists of two statements:
> Collection c = ejb.findByWhatver(...);
> and
> Iterator i = c.iterator();
>
> When the finder is called the container will create the collection and
> put the results (remote or local interfaces of the selected entity
> beans) in it.
> So by the time the iterator is created they are already cached.
>
> Regards,
> Dies
>
> > A question which is bothering me last time is: does EJB container able
> > to read-ahead the collection of entities just have returned to the
> > client? It will be great if it's implemented in whatever J2EE
> > compliant AS!
> > For example if client calls finder method and iterates the collection
> > of entities:
> > Iterator i = ejb.findByWhatver(...).iterator();
> > while (i.hasNext()) { ... }
> > then EJB container iterate this collection also to cache entities and
> > make this 'while' faster.
> > Does it implemented anywhere?
> >
> > ---
> > Kirill Mikhailov
> >
>
>
===========================================================================
> 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".
>
>
===========================================================================
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".
