open class LocalStatelessSessionProxyFactoryBean : LocalSlsbInvokerInterceptor, FactoryBean<Any>, BeanClassLoaderAware
Convenient FactoryBean for local Stateless Session Bean (SLSB) proxies. Designed for EJB 2.x, but works for EJB 3 Session Beans as well.
See org.springframework.jndi.JndiObjectLocator for info on how to specify the JNDI location of the target EJB.
If you want control over interceptor chaining, use an AOP ProxyFactoryBean with LocalSlsbInvokerInterceptor rather than rely on this class.
In a bean container, this class is normally best used as a singleton. However, if that bean container pre-instantiates singletons (as do the XML ApplicationContext variants) you may have a problem if the bean container is loaded before the EJB container loads the target EJB. That is because by default the JNDI lookup will be performed in the init method of this class and cached, but the EJB will not have been bound at the target location yet. The best solution is to set the "lookupHomeOnStartup" property to "false", in which case the home will be fetched on first access to the EJB. (This flag is only true by default for backwards compatibility reasons).
Author
Rod Johnson
Author
Colin Sampaleanu
Since
09.05.2003
See Also
AbstractSlsbInvokerInterceptor#setLookupHomeOnStartupAbstractSlsbInvokerInterceptor#setCacheHome
LocalStatelessSessionProxyFactoryBean()
Convenient FactoryBean for local Stateless Session Bean (SLSB) proxies. Designed for EJB 2.x, but works for EJB 3 Session Beans as well. See org.springframework.jndi.JndiObjectLocator for info on how to specify the JNDI location of the target EJB. If you want control over interceptor chaining, use an AOP ProxyFactoryBean with LocalSlsbInvokerInterceptor rather than rely on this class. In a bean container, this class is normally best used as a singleton. However, if that bean container pre-instantiates singletons (as do the XML ApplicationContext variants) you may have a problem if the bean container is loaded before the EJB container loads the target EJB. That is because by default the JNDI lookup will be performed in the init method of this class and cached, but the EJB will not have been bound at the target location yet. The best solution is to set the "lookupHomeOnStartup" property to "false", in which case the home will be fetched on first access to the EJB. (This flag is only true by default for backwards compatibility reasons). |
open fun afterPropertiesSet(): Unit |
|
open fun getBusinessInterface(): Class<*>
Return the business interface of the EJB we're proxying. |
|
open fun getObject(): Any |
|
open fun getObjectType(): Class<*> |
|
open fun isSingleton(): Boolean |
|
open fun setBeanClassLoader(classLoader: ClassLoader): Unit |
|
open fun setBusinessInterface(businessInterface: Class<*>): Unit
Set the business interface of the EJB we're proxying. This will normally be a super-interface of the EJB local component interface. Using a business methods interface is a best practice when implementing EJBs. |