Forgive me if Im missing the point here but what would be the point of caching home objects in a Session Bean which you could only access by looking up its Home Interface via JNDI i.e. The very thing you are trying to avoid.
regards DGA -----Original Message----- From: A mailing list for Enterprise JavaBeans development [mailto:[EMAIL PROTECTED]] On Behalf Of Rickard Sent: 13 February 2002 11:02 To: [EMAIL PROTECTED] Subject: Re: [EJB-INT] Home Object Caching Giju Thomson wrote: > I have found out that the most time taken in a ejb lifecycle is at > JDNI Lookup . So if we can cache the home object then it will be much > faster . How can we cache the home object ? What is the best algo to > implement a object cache . Which would be better the cache as a MBean or > as a SessionBean ? Try both ways, benchmark them, and pick the fastest one. /Rickard -- Rickard �berg Author of "Mastering RMI" Chief Architect, TheServerSide.com The Middleware Company - We Build Experts! ======================================================================== === 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".
