I am invoking a remote bean session from a J2SE application and would like to cache the link to the bean session to reduce the cost of the search. This is normal?
In EJB2, the ServiceLocator pattern was commonly used to cache requests for remote resources, but EJB3 does not have a separate EJB Home (usually cached) and remote objects.
In general, the general answer to this is to use EJB3 injection, but since I am making a remote EJB server call from a J2SE client, I cannot use injection.
source
share