org.springframework.ejb.support Documentation Differences

This file contains all the changes in documentation in the package org.springframework.ejb.support as colored differences. Deletions are shown like this, and additions are shown like this.

If no deletions or additions are shown in an entry, the HTML tags will be what has changed. The new HTML tags are shown in the differences. If no documentation existed, and then some was added in a later version, this change is noted in the appropriate class pages of differences, but the change is not shown on this page. Only changes in existing text are shown here. Similarly, documentation which was inherited from another class or interface is not shown here.

Note that an HTML error in the new documentation may cause the display of other documentation changes to be presented incorrectly. For instance, failure to close a <code> tag will cause all subsequent paragraphs to be displayed differently.

Base class for Spring-based EJB 2.x beans. Not intended for direct subclassing: Extend AbstractStatelessSessionBean, AbstractStatefulSessionBean or AbstractMessageDrivenBean instead.

Provides a standard way of loading a Spring BeanFactory. Subclasses act as a facade, with the business logic deferred to beans in the BeanFactory. Default is to use a org.springframework.context.access.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, e.g. in setSessionContext). For use of a shared ApplicationContext between multiple EJBs, where the container class loader setup supports this visibility, you may instead use a org.springframework.context.access.ContextSingletonBeanFactoryLocator. Alternatively, .setBeanFactoryLocator may be called with a custom implementation of the org.springframework.beans.factory.access.BeanFactoryLocator interface.

Note that we cannot use final for our implementation of EJB lifecycle methods, as this would violate the EJB specification. @author Rod Johnson @author Colin Sampaleanu @author Juergen Hoeller @see org.springframework.context.access.ContextJndiBeanFactoryLocator @see org.springframework.context.access.ContextSingletonBeanFactoryLocatorContextSingletonBeanFactoryLocator @deprecated as of Spring 3.2, in favor of implementing EJBs in EJB 3 style

Convenient base class for JMS-based EJB 2.x MDBs. Requires subclasses to implement the JMS javax.jms.MessageListener interface. @author Rod JohnsonJohnson @deprecated as of Spring 3.2, in favor of implementing EJBs in EJB 3 style

Convenient base class for EJB 2.x 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-arg ejbCreate() method as required by the EJB specification. This ejbCreate() method loads a BeanFactory, before invoking the onEjbCreate() method, which is supposed to contain subclass-specific initialization.

NB: We cannot use final methods to implement EJB API methods, as this violates the EJB specification. However, there should be no need to override the setMessageDrivenContext or ejbCreate() methods. @author Rod JohnsonJohnson @deprecated as of Spring 3.2, in favor of implementing EJBs in EJB 3 style

Base class for Spring-based EJB 2.x session beans. Not intended for direct subclassing: Extend AbstractStatelessSessionBean or AbstractStatefulSessionBean instead.

This class saves the session context provided by the EJB container in an instance variable and exposes it through the SmartSessionBean interface. @author Rod Johnson @author Juergen HoellerHoeller @deprecated as of Spring 3.2, in favor of implementing EJBs in EJB 3 style

Convenient base class for EJB 2.x stateful session beans (SFSBs). 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 which is not serializable, subclasses must call setBeanFactoryLocator(null) in ejbPassivate(), with a corresponding call to setBeanFactoryLocator(xxx) in ejbActivate() unless relying on the default locator. @author Rod Johnson @author Colin Sampaleanu @see org.springframework.context.access.ContextJndiBeanFactoryLocatorContextJndiBeanFactoryLocator @deprecated as of Spring 3.2, in favor of implementing EJBs in EJB 3 style