Home >> All >> org >> springframework >> ejb >> [ support Javadoc ]

• org.springframework.ejb.support: Javadoc index of package org.springframework.ejb.support.


Package Samples:

• org.springframework.ejb.support

Classes:

• AbstractEnterpriseBean: Superclass for all EJBs. Package-visible: not intended for direct subclassing. Provides a standard way of loading a BeanFactory. Subclasses act as a facade, with the business logic deferred to beans in the BeanFactory. Default is to use a ContextJndiBeanFactoryLocator, which will initialize an XML ApplicationContext from the class path (based on a JNDI name specified). For a different locator strategy, setBeanFactoryLocator may be called ( before your EJB's ejbCreate method is invoked, for example, in setSessionContext ). For use of a shared ApplicationContext between multiple EJBs, where the container ...
• AbstractStatelessSessionBean: Convenient superclass for stateless session beans (SLSBs), minimizing the work involved in implementing an SLSB and preventing common errors. Note that SLSBs are the most useful kind of EJB. As the ejbActivate() and ejbPassivate() methods cannot be invoked on SLSBs, these methods are implemented to throw an exception and should not be overriden by subclasses. (Unfortunately the EJB specification forbids enforcing this by making EJB lifecycle methods final.) There should be no need to override the setSessionContext() or ejbCreate() lifecycle methods. Subclasses are left to implement the onEjbCreate() ...
• AbstractStatefulSessionBean: Convenient superclass for stateful session beans. SFSBs should extend this class, leaving them to implement the ejbActivate() and ejbPassivate() lifecycle methods to comply with the requirements of the EJB specification. Note: Subclasses should invoke the loadBeanFactory() method in their custom ejbCreate and ejbActivate methods, and should invoke the unloadBeanFactory() method in their ejbPassivate method. Note: The default BeanFactoryLocator used by this class's superclass (ContextJndiBeanFactoryLocator) is not serializable. Therefore, when using the default BeanFactoryLocator, or another variant ...
• AbstractMessageDrivenBean: Convenient superclass for MDBs. Doesn't require JMS, as EJB 2.1 MDBs are no longer JMS-specific: see the AbstractJmsMessageDrivenBean subclass. This class ensures that subclasses have access to the MessageDrivenContext provided by the EJB container, and implement a no argument ejbCreate() method as required by the EJB specification. This ejbCreate() method loads a BeanFactory, before invoking the onEjbCreate() method, which should contain subclass-specific initialization. NB: We cannot use final methods to implement EJB API methods, as this violates the EJB specification. However, there should ...
• AbstractSessionBean: Superclass for all session beans. Not intended for direct client subclassing; derive from AbstractStatelessSessionBean or AbstractStatefulSessionBean instead. This class saves the session context provided by the EJB container in an instance variable and provides a NOP implementation of the ejbRemove() lifecycle method.
• SmartSessionBean: Interface to be implemented by Session Beans that want to expose important state to cooperating classes. Implemented by Spring's AbstractSessionBean class and hence by all of Spring's specific Session Bean support classes.
• AbstractJmsMessageDrivenBean: Convenient superclass for JMS MDBs. Requires subclasses to implement the JMS interface MessageListener.

Home | Contact Us | Privacy Policy | Terms of Service