The JNDIKernelRegistryPlugin is to used for the jndi: dependencies (which is a MC context) that are added to the EJB containers which are installed as MC beans. When MC internally, changes the state of the contexts, there are multiple calls to the :
public KernelRegistryEntry getEntry(Object name)
API. The jndi: dependencies point to proxy factories bound to JNDI and when this API is called it results in a JNDI lookup and a subsequent proxy/session creation. This needs to be avoided
- relates to
-
EJBTHREE-1800 Improve EJB3 deployment time on AS5
- Resolved