1 Reply Latest reply on Dec 7, 2011 11:07 AM by Christian Sadilek

    Deployment errors in project based on Errai 2.0

    slawek t Novice

      Hi,

       

      I switched from Errai 1.3.1 to 2.0-SNAPSHOT and my project was deploying with no issues, but now the same project gives me a stacktrace:

       

      09:09:10,628 ERROR [org.apache.catalina.core.ContainerBase.[jboss.web].[default-host].[/dms]] (MSC service thread 1-5) Servlet /dms threw load() exception: javax.naming.NameNotFoundException; remaining name 'java:comp/BeanManager'

                at org.mortbay.naming.NamingContext.lookup(NamingContext.java:634) [jetty-naming-6.1.25.jar:]

                at org.mortbay.naming.NamingContext.lookup(NamingContext.java:680) [jetty-naming-6.1.25.jar:]

                at org.mortbay.naming.local.localContextRoot.lookup(localContextRoot.java:164) [jetty-naming-6.1.25.jar:]

                at javax.naming.InitialContext.lookup(InitialContext.java:411) [:1.7.0_01]

                at org.jboss.errai.cdi.server.Util.lookupBeanManager(Util.java:187) [errai-weld-integration-2.0-20111207.043209-15.jar:]

                at org.jboss.errai.cdi.server.CDIServiceLocator.locateService(CDIServiceLocator.java:15) [errai-weld-integration-2.0-20111207.043209-15.jar:]

                at org.jboss.errai.bus.server.servlet.AbstractErraiServlet.init(AbstractErraiServlet.java:98) [errai-bus-2.0-20111207.035349-21.jar:]

                at org.apache.catalina.core.StandardWrapper.loadServlet(StandardWrapper.java:1202) [jbossweb-7.0.1.Final.jar:7.0.2.Final]

                at org.apache.catalina.core.StandardWrapper.load(StandardWrapper.java:1102) [jbossweb-7.0.1.Final.jar:7.0.2.Final]

                at org.apache.catalina.core.StandardContext.loadOnStartup(StandardContext.java:3631) [jbossweb-7.0.1.Final.jar:7.0.2.Final]

                at org.apache.catalina.core.StandardContext.start(StandardContext.java:3844) [jbossweb-7.0.1.Final.jar:7.0.2.Final]

                at org.jboss.as.web.deployment.WebDeploymentService.start(WebDeploymentService.java:70) [jboss-as-web-7.0.2.Final.jar:7.0.2.Final]

                at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1824) [jboss-msc-1.0.1.GA.jar:1.0.1.GA]

                at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1759) [jboss-msc-1.0.1.GA.jar:1.0.1.GA]

                at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110) [:1.7.0_01]

                at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603) [:1.7.0_01]

                at java.lang.Thread.run(Thread.java:722) [:1.7.0_01]

       

       

      I'm deploying on jboss as 7 (also in development mode) and I don't understand why org.mortbay.naming.* package has it's place even though a jetty is not involved.