Hi,
We have a service Locator that does all JNDI lookups for a session bean.
Now we want to put a caching mechanism to save us from doing the JNDI look up again and again.
1. Can we cache the home interfaces of both Session and Entity Beans ? I mean is there a potential problem of doing it this way.
2. This caching is done by caching the handle generally , is there a different way of doing it?
Thanx.
-
Caching EJB Handles. (3 messages)
- Posted by: Ritesh Biswas
- Posted on: October 05 2001 10:07 EDT
Threaded Messages (3)
- Caching EJB Handles. by Abhijit Gaikwad on October 06 2001 04:29 EDT
- Caching EJB Handles. by John O'Reilly on October 09 2001 09:26 EDT
- Caching EJB Handles. by sumev kohli on October 11 2001 11:32 EDT
-
Caching EJB Handles.[ Go to top ]
- Posted by: Abhijit Gaikwad
- Posted on: October 06 2001 04:29 EDT
- in response to Ritesh Biswas
Hi ,
What ever you want to do is a one of the Patterns specified by Sun . It is called as Hook Pattern .
For details visit java.sun.com
-- @bhijit
-
Caching EJB Handles.[ Go to top ]
- Posted by: John O'Reilly
- Posted on: October 09 2001 09:26 EDT
- in response to Abhijit Gaikwad
Hi,
I couldn't find a reference to the "Hook" pattern on java.sun.com. Is it the same/similar to the "Service Locator" pattern?
Rgds,
John -
Caching EJB Handles.[ Go to top ]
- Posted by: sumev kohli
- Posted on: October 11 2001 11:32 EDT
- in response to Ritesh Biswas
Service Locator pattern talks about caching at client end but if you look at Application Server - e.g. WebSphere, it has provided certain properties for caching !! (I couldn't find same in weblogic though both of them implement JNDI)
com.ibm.websphere.naming.PROPS
--> one of the other points which I am just wondering is by using Singleton we are avoiding Object overhead but at the same time all the simultaneous request for context have to wait ???