EJB design: EJB3 service locator/business delegate caching

  1. EJB3 service locator/business delegate caching (1 messages)

    Can any1 tell me how caching works in service locator using EJB3? Specifically how long can I hold on to stateless session beans? I believe the old fashion EJB2 way was to cache the home interface once looked up using the initial jndi context. Is there anything left to cache with EJB3?
  2. Anyone care to answer?[ Go to top ]

    I too would like to know if this makes sense in the EJB 3 world - I'm perplexed about caching a reference to the Session bean. Would this result in better performance? Would it enforce the use of the same instance, thus negating the benefits of the pool?