Yes, my mistake for not phrasing it correctly.
arkin
Gene De Lisa wrote:
>
> The phrase "It can be the actual entity bean" is misleading. I know what
> you're saying from your reply but the original statement would probably be
> misunderstood by many people.
>
> The second thing *is* in the spec. It (scalability) is the reason that
> find/activate/load are separate things. Doing a find gives the client a
> rr[s] to ejbobject[s] (ok, stubs etc.). If the design is stupid enough to do
> something like "findEverythingInTheUniverse" then the server won't die
> (knock wood) because it doesn't *have* to associate a bean instance with
> every ejbobject right then.
> activate/ejbLoad has to take place somehow before a business method. You can
> say for sure that will happen (disregarding container bugs)
>
> How the server fiddles around with caching etc is up to them (thats the part
> not in the spec)
>
> gene
>
> > Sorry, I wans't talking about remote references, but the ability to
> > reference the bean and have an instance in the server. That instance is
> > activated (i.e. not in the pool), but is not loaded until you actually
> > use it for the first time.
> >
> > It's not an EJB specification, but one way an EJB server can implement
> > lazy loading for scalability.
> >
> > arkin
> >
> >
> > Gene De Lisa wrote:
> > >
> > > Nope. Clients never ever ever get remote references to beans.
> > >
>
> arkin:
> > > > It can be the actual entity bean. The bean can be activated
> > and you can
> > > > reference it, but until you call a business method it will not be
> > > > loaded.
> > > >
--
----------------------------------------------------------------------
Assaf Arkin www.exoffice.com
CTO, Exoffice Technologies, Inc. www.exolab.org
===========================================================================
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".
