At 07:34 AM 2/26/99 +0100, Rickard �berg wrote:
>Yes, Home lookup can be slow if you have to do it through JNDI every
>time. But you don't have to do it every time.
>
>Two solutions:
>1) In the setSessionContext() simply lookup the Home-object and store it
>in a variable
But its not serializable so passivate will junk it. And also
setSessionContext() will give me my home rather than the home of the entity?
><plug>
>2) In the setSessionContext() simply create a SmartProxy to the Home.
> Same effect as above, but you also don't
> * have to do the lookup manually
> * if the Home object becomes unavailable the proxy will automatically
>relookup it, thus making it fault-tolerant
>For download of the SmartProxy package please see my homepage.
></plug>
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?
andy
===========================================================================
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".
