4 Replies Latest reply on Oct 27, 2006 5:56 PM by Arpad Sooky

    JNDI Problems by deploying an EJB 3 stateless session bean

    Endre Gaspar Newbie


      If I'm deploying a stateless session bean it works fine at first,
      there is no problem during the deployment.
      But I cannot access it!!
      If I'm looking on the JNDIView using the JMX Console so I have the following:

      +- testejb301-0.1 (class: org.jnp.interfaces.NamingContext)
      | +- UsersDao (class: org.jnp.interfaces.NamingContext)
      | | +- local (proxy: $Proxy70 implements No ClassLoaders found for: at.own.ejb3.test.UsersDao (no security manager: RMI class loader disabled))
      | +- UsersServiceBean (class: org.jnp.interfaces.NamingContext)
      | | +- remote (proxy: $Proxy72 implements No ClassLoaders found for: at.own.ejb3.test.UsersServiceRemote (no security manager: RMI class loader disabled))

      I've newer experienced such a problem with ejbs on jboss yet!!
      This java code is still working:
      Object ref = jndiContext.lookup("testejb301-0.1/UsersServiceBean");
      but the following not:

      Does it have anybody know any reason to this problem??
      I've downloaded and installes the newest jboss server with the EJB 3.0 container.

      Thanks and Regards,