4 Replies Latest reply on Jun 28, 2007 10:03 AM by phantom

    Dispatcher not bound

    phantom

      Good day,

      I cann't run my application due to this excaption:

      16:25:23,866 ERROR [DebugPageHandler] redirecting to debug page
      javax.naming.NameNotFoundException: Dispatcher not bound
       at org.jnp.server.NamingServer.getBinding(NamingServer.java:529)
       at org.jnp.server.NamingServer.getBinding(NamingServer.java:537)
       at org.jnp.server.NamingServer.getObject(NamingServer.java:543)
       at org.jnp.server.NamingServer.lookup(NamingServer.java:267)
       at org.jnp.server.NamingServer.lookup(NamingServer.java:270)
       at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:625)
       at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:587)
       at javax.naming.InitialContext.lookup(InitialContext.java:351)
       at org.jboss.seam.Component.instantiateSessionBean(Component.java:1107)
       at org.jboss.seam.Component.instantiate(Component.java:1093)
       at org.jboss.seam.Component.newInstance(Component.java:1736)
       at org.jboss.seam.Component.getInstance(Component.java:1643)
       at org.jboss.seam.Component.getInstance(Component.java:1610)
       at org.jboss.seam.Component.getInstance(Component.java:1589)
       at org.jboss.seam.Component.getInstance(Component.java:1584)
       at org.jboss.seam.core.Dispatcher.instance(Dispatcher.java:238)
       at org.jboss.seam.interceptors.AsynchronousInterceptor.aroundInvoke(Asyn
      chronousInterceptor.java:26)
       at org.jboss.seam.intercept.SeamInvocationContext.proceed(SeamInvocation
      Context.java:69)
      


      I read this
      http://www.jboss.com/index.html?module=bb&op=viewtopic&t=97033

      But I use Jboss AS and my application packaged as EAR. That is mean, that I have one submodule for EJBs and one for WAR. I can't understand what is the problem in. May be I switched off something important in config?

      Please help me!

        • 1. Re: Dispatcher not bound
          pmuir

          Add a

          <core:dispatcher />
          (Seam 1.2.1.GA) or
          <async:dispatcher />
          (Seam2) to components.xml

          • 2. Re: Dispatcher not bound
            phantom

            But I have already this line in my components.xml.
            As you can see this exception rised during instantiating of the session bean Dispatcher.
            May be I can instantiate by that line:

            <core:dispatcher name="Dispatcher"/>

            ?

            It seams, that I know where the problem. I have seams jars in /lib and /deploy/jbossweb-tomcat5.5/jsf-libs/ directories. Am I correct that this error may occure due to imposibility in instantiate SessionLess library from that directories?

            • 3. Re: Dispatcher not bound
              pmuir

              Yes, you certainly don't want jboss-seam.jar in either of those places.

              • 4. Re: Dispatcher not bound
                phantom

                Ok. Thank you!

                I place Seams jars to that directories to share it among several Seams projects on one instance of Jboss AS.