Yes, the ejbLoad's on the individual beans will have to be called at
transaction edge (per the spec), but at least this will happen all at
once on the server, and not while pinging and ponging back and forth
to the client.
Assuming we are talking rdbms here, they are pretty good at caching
so even with BMP we shouldn't be in too bad of shape, and with CMP
vendors will do fancy things with cursors and caches so that the
ejbLoad impact is minimal.
-Chris.
> -----Original Message-----
> From: Sachin Aggarwal [SMTP:[EMAIL PROTECTED]]
> Sent: Tuesday, June 15, 1999 3:14 PM
> To: [EMAIL PROTECTED]
> Subject: Using collection bean to represent a list of entity beans-
> was RE : Application Server container related question
>
> I've followed most of the threads on the collection of beans as a bean and
> have some related questions.Here's one of them.
>
> Say we have instantiated a bean representing the collection of say 'Item'
> beans and return a remote reference to the client. When the client asks
> for
> some info on the list of items, then is the assumption that the collection
> bean has a list of references of the item entities but it iterates over
> them
> on the server side and returns a list of data objects to the client ?
> Assuming this is true, then when the client makes a new call to the same
> colection bean in a new transaction but wants different data from the same
> collection of item entities , then won't that require that the collection
> bean reload all the item entities ? *unless* the item entities are still
> cached !
>
> Looks to me like for this scenario where we are querying the same
> collection, the caching of beans becomes important and the idle time for
> the
> entity beans needs to be set high enough that they don't get passivated.
>
> So would you agree that caching can be an issue even when the server
> returns
> objects by value to clients?
>
>
> > -----Original Message-----
> > From: A mailing list for Enterprise JavaBeans development
> > [mailto:[EMAIL PROTECTED]]On Behalf Of Chris Raber
> > Sent: Tuesday, June 15, 1999 9:42 AM
> > To: [EMAIL PROTECTED]
> > Subject: Re: Application Server container related question
> >
> >
> > The behavior you are seeing is as expected. Accessing finders and
> > iterating the results from remote clients is not recommended. As an
> > alternative, see the various message threads in the archives for this
> > list concerning return objects by value to clients, or implementing
> > collections of beans as beans themselves.
> >
> > -Chris.
> >
> > Patient: "Doctor, it hurts when I stick my finger in my ear".
> >
> > Doctor: "Stop sticking your finger in your ear".
> >
> >
> > > -----Original Message-----
> > > From: Manisha Umbarje [SMTP:[EMAIL PROTECTED]]
> > > Sent: Monday, June 14, 1999 12:37 PM
> > > To: [EMAIL PROTECTED]
> > > Subject: Application Server container related question
> > >
> > > Hi,
> > >
> > > I am new on this EJB interest group.. I don't know if this issue has
> > > already been discussed. I have been trying to access Bean
> > Managed Entity
> > > Bean's remote methods from the servlet. I have implemented
> > the method
> > > ejbFindByName() which returns Enumeration of Primary Key
> > class of the
> > > Entity Bean and then I try to execute different methods on
> > this object.
> > > But when I do so, I observed in the trace file of my
> > application server
> > > that container is making calls to ejbLoad() every time I
> > try to call
> > > remote method. It seems that Container is trying to
> > synchronize Bean's
> > > state to DB state.
> > >
> > > That makes my application very slow.
> > >
> > > Is this way it should behave or am I missing something ?
> > >
> > > Manisha
> > >
> > >
> > ==============================================================
> > ============
> > > =
> > > 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".
> >
> >
>
> ==========================================================================
> =
> 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".
