Caching reference to home

Question

I want to cache JNDI Look ups for EJBs.
I will do a look up for the EJBs at class loading and then cache them in the memory.
This will only be done on
the server side i.e both the client and EJBs are on server side (so securing JNDI
look up is not of any concern). Will clustering of
server (same of different machine) have a effect on this caching mechanism. As
JNDI service corresponds
to a server instance. I am on WL 5.1 with service pack 8
Also is there a way where I can do a lookup of multiple EJBs in a single lookup
call. May be like giving
a list of beans to be looked up as parameter. Using common intial context (reference
to JNDI tree), I want to
achieve this lookup in a single call. All this will be done statically (during
class loading) and cached in memory.
Thanks
Mohit

Answer 1

1. With WL, no problem config'ing and caching as you specified
2. No way to multi lookup
Peace,
Cameron Purdy
Tangosol, Inc.
http://www.tangosol.com
+1.617.623.5782
WebLogic Consulting Available
"M Segi" <[email protected]> wrote in message
news:3af6b66d$[email protected]..
>
I want to cache JNDI Look ups for EJBs.
I will do a look up for the EJBs at class loading and then cache them inthe memory.
This will only be done on
the server side i.e both the client and EJBs are on server side (sosecuring JNDI
look up is not of any concern). Will clustering of
server (same of different machine) have a effect on this cachingmechanism. As
JNDI service corresponds
to a server instance. I am on WL 5.1 with service pack 8
Also is there a way where I can do a lookup of multiple EJBs in a singlelookup
call. May be like giving
a list of beans to be looked up as parameter. Using common intial context(reference
to JNDI tree), I want to
achieve this lookup in a single call. All this will be done statically(during
class loading) and cached in memory.
Thanks
Mohit