Re: Home Object Caching

[Divya]

Try using "Service Locator Pattern"   The solution for the redundant and expensive JNDI lookup process problem is to cache those service objects when the client performs JNDI lookup first time and reuse that service object from the cache second time onwards for other clients.This technique maintains a cache of service objects and looks up the JNDI only first time for a service object. This technique reduces redundant and expensive JNDI lookup process thus increasing performance significantly. Service Locator Pattern implements this technique by having a class to cache service objects, methods for JNDI lookup and methods for getting service objects from the cache.   Best Regards, Divya.     ----- Original Message ----- From: Giju Thomson To: [EMAIL PROTECTED] Sent: Wednesday, February 13, 2002 4:18 PM Subject: Home Object Caching Hi All ,     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 ? Thanking you in advance . Cheers Thomson Do You Yahoo!? Send FREE Valentine eCards with Yahoo! Greetings!