0 Replies Latest reply on Feb 23, 2012 4:31 PM by Brandon Atkinson

    Are ejb-related JNDI bindings supposed to be visible in jndi-view?

    Brandon Atkinson Newbie

      I'm deploying a version 2.1 ejb, and I get a bunch of binding information back regarding JNDI binding locations:

       

      16:16:29,166 INFO  [org.jboss.as.ejb3.deployment.processors.EjbJndiBindingsDeploymentUnitProcessor] (MSC service thread 1-11) JNDI bindings for session bean named AnonymousBean in deployment unit deployment "anonymous-ejb.jar" are as follows:

                java:global/anonymous-ejb/AnonymousBean!packagename.AnonymousBeanRemote

                java:app/anonymous-ejb/AnonymousBean!packagename.AnonymousBeanRemote

                java:module/AnonymousBean!packagename.AnonymousBeanRemote

                java:jboss/exported/anonymous-ejb/AnonymousBean!packagename.AnonymousBeanRemote

                java:global/anonymous-ejb/AnonymousBean!packagename.AnonymousBeanHome

                java:app/anonymous-ejb/AnonymousBean!packagename.AnonymousBeanHome

                java:module/AnonymousBean!packagename.AnonymousBeanHome

                java:jboss/exported/anonymous-ejb/AnonymousBean!packagename.AnonymousBeanHome

       

      I then connect with the admin-cli, and do a jndi-view:

       

      [standalone@localhost:9999 /] /subsystem=naming:jndi-view

      ....

                  "java:global" => {"anonymous-ejb" => {

                      "class-name" => "javax.naming.Context",

                      "children" => undefined

                  }}

      ....

       

      Somehow, I expected that the EJB would be visible in jndi, given the jndi related log messages and the fact the the ejb successfully deployed.

       

      Is this expected behavior?  I'm having issues depending on the EJB as well, so my suspicion is that the bean is not being bound to JNDI after all.