|
From: Colin S. <col...@ex...> - 2004-01-17 21:40:25
|
Currently AbstractJndiLocator does the JNDI lookup right after initialization, basically triggered by afterPropertiesSet. Somebody in the SF forum is having an issue when loading a J2EE ear in weblogic, in that the webapp is loaded by WL before the EJBs. Since the webapp triggers loading the context, and the EJB invoker interceptors (derived from AbstractJndiLocator) are singletons and are created at that time, they do the JNDI lookups for the ejb homes at that time, and don't see anything because the EJBs are not there yet. What would probably work is to have the option of lazily doing the JNDI lookup. It would stay non-lazy by default, but subclasses, like the ejb invokers, would be lazy by default. |