Version 6
Created by alrubinger on Dec 18, 2007 1:52 AM. Last modified by alrubinger on Jan 20, 2011 4:35 AM.

    Migrating to EJB3 Module Bundled with JBoss AS 5.0.0.Beta3

     

    • All JBoss EJB3 Annotations extending the JEE API are located in a new artifact, jboss-ejb3-ext-api.jar, located in $JBOSS_HOME/client.  See Why don't my AS 4.2.x @Service beans deploy in AS 5+? for more information on how this may affect you.

    • All JBoss EJB3 Annotations extending the JEE API have been moved to a new, singluar namespace, "org.jboss.ejb3.annotation".  See Why don't my AS 4.2.x @Service beans deploy in AS 5+? for more information on how this may affect you.

    • Implementations for Cache Implementations, Pool Implementations, Remote Proxy Implementations, and Persistence Manager Implementations are configured as Strings in $JBOSS_HOME/server/[ServerName|DOC-12210]/deployers/ejb3.deployer/META-INF/ejb3-deployers-beans.xml

      • @CacheConfig.name (NoPassivationCache | SimpleStatefulCache | StatefulTreeCache)

      • @Pool.value (ThreadlocalPool | StrictMaxPool)

        • Defaults in org.jboss.ejb3.annotation.defaults.PoolDefaults

      • @PersistenceManager.value (StatefulSessionFilePersistenceManager)

        • Defaults in org.jboss.ejb3.annotation.defaults.PersistenceManagerDefaults

      • @RemoteBinding.factory (RemoteProxyFactory | IORFactory | ServiceRemoteProxyFactory | StatefulClusterProxyFactory | StatefulRemoteProxyFactory | StatelessClusterProxyFactory | StatelessRemoteProxyFactory)

        • Defaults in org.jboss.ejb3.annotation.defaults.RemoteBindingDefaults

    • EJB 2.1 View requirements

      • Home extending EJBLocalHome or EJBHome must be defined

      • Remote or Local interface must either be defined via @Local/@Remote or via return type of "create<METHOD>" methods of the Home

      • EJB 2.1 Remote/Local interfaces must extend EJBObject/EJBLocalObject

    • @Local/@Remote may be used to define either EJB 3.0 View Business Interface, or EJB 2.1 View Remote/Local interface

    • EJB3 Artifacts in "deploy" directory before Server Startup will lead to an error in the Timer Service initialization, see http://jira.jboss.com/jira/browse/EJBTHREE-1173