EJB3.0 and caching
there was a good idea to use the servicelocator pattern in ejb 2.1, mainly to solve the time for home interfaces creation through caching.
i still can't find any design patterns targeting ejb 3.0, so i'd like to hear this forum's gurus opinion on the caching issue in ejb 3.0. it seems to me the new model doesn't include any caching mechanism and each @EJB injection makes the whole lookup process behind the scene. do you think it might be a good idea to cache and reuse the objects created by the means of @EJB injection? my first thinking was that this might be wrong, because we are talking about the remote and not home here. but then i realize that this terminology is gone with ejb 2.1. it's just a poji now, we can cache it as a reference of any other type...
thanks for your ideas!