Caching references is one of the common techniques used in j2ee apps. Have
a look at the service locator pattern:
http://java.sun.com/blueprints/patterns/ServiceLocator.html

Usually home interfaces are cached. There may be unwanted consequence of
caching reference for a remote interface for a stateless session bean. You
may end up making client code aware of the nature of the bean (like
stateless/stateful). Also, all the security and transaction contexts will
become an issue if the same stateless remote object is accessed by more
than one client.

-karthik.

> Hi,
>
> I know that the stateful session bean remote object
> reference can be cached in the web tier session for
> maintaining conversation state. I wonder if a
> stateless
> bean's remote object reference can be cached in web
> tier session for reusing so no need to lookup home and
>
> create remote object again. Does it make sense?
>
> Thanks.
>
> pw
>

====================================================================
Companion Site: http://www.corej2eepatterns.com
J2EE BluePrints: http://java.sun.com/blueprints/corej2eepatterns
List Archive: http://archives.java.sun.com/archives/j2eepatterns-interest.html
Unsubscribing: email "signoff J2EEPATTERNS-INTEREST" to listserv@(protected)