> -----Original Message-----
> From: Rickard �berg [SMTP:[EMAIL PROTECTED]]
> Sent: Friday, February 26, 1999 9:49 PM
>
> Andy Piper wrote:
> > But its not serializable so passivate will junk it. And also
> > setSessionContext() will give me my home rather than the home of the
> entity?
>
> You've got it backwards:
> 1) Stateless session beans don't get passivated
> 2) You can keep references to whatever you want (for example the Home of
> an EntityBean)
>
> > Ok, so here I'm caching the result of the lookup and if ejbPassivate()
> > junks it then I get it again? This seem better but in a large,
> multi-user
> > system, passivation is quite likely is it not?
>
> Not with stateless beans. What's to passivate??
[>] Not passivated. But might my client talk to different stateless
session bean instances between service calls? Doesn't the same problem
appear?
Danny.
===========================================================================
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".
