1 Reply Latest reply on Mar 7, 2011 10:47 AM by Arnie Morein

    Working Seam app on JAS 4.3 fails on 5.1

    Arnie Morein Newbie

      I have a Seam 2.2.1.CR1 app that works fine on JBoss EPP 4.3.0. When I port and recompile it over to EPP 5.1, which uses Seam 2.2.2.EAP5, the code that is started as part of org.jboss.seam.postInitialization fails because another Seam SLSB that acts as an EJB wrapper cannot be created - because its related EJB name is not bound.

      But a few lines up in the log it shows the EJB being deployed successfully.

      installing bean: jboss.j2ee:ear=ade-ear-1.0.0.ear,jar=ade-ejb.jar,name=EjbDaoFacadeImpl,service=EJB3
        with dependencies:
        and demands:
        and supplies:
      Added bean(jboss.j2ee:ear=ade-ear-1.0.0.ear,jar=ade-ejb.jar,name=EjbDaoFacadeImpl,service=EJB3) to KernelDeployment of: ade-ejb.jar

      Excerpt from failing Seam POJO:

      public class SeamInitializationObserver {

      protected EjbDaoFacade ejbDaoFacade;


      SysParameterMap sysParameterMap = new SysParameterMap();

      The EJB that isn't bound:

      public class EjbDaoFacadeImpl implements EjbDaoFacade {

      I have tried putting the Seam POJO name on the Stateless and LocalBinding annotations to no avail.

      Has something changed on AS 5.1 or in Seam 2.2.2.EAP5 that would not let a locally deployed EJB not be available until the WAR is completely deployed and functional?