EJB not getting bound to JNDI name using Sun App Server upon deployment

Question

Hello,
I've created a very simple "HelloWorld" EJB (2.1-style) and have successfully deployed it to my local application server (Sun Java System App Server Platform Edition 9.0). I now want to invoke the EJB (I have single stateless session bean that returns a string) using a simple remote client app (the client app is executing outside of the app server within its own JVM).
From my client app I am able to create the InitialContext object, but I get error when trying to lookup my EJB's home object. My client looks as follows:
               jndiProperties = new Properties();
               jndiProperties.put("java.naming.factory.initial",
                    "com.sun.jndi.cosnaming.CNCtxFactory");
               jndiProperties.put("java.naming.provider.url",
                    "iiop://localhost:3700"); // ORB listener is listening on port 3700...
               context = new InitialContext(jndiProperties);
               home = context.lookup("ejb/HelloWorldEJB"); // this line throws an exception (line 54)
               ...The exception I receive is:
               [java] 234  ERROR [main] net.blueslate.sample.ejb.helloworld.HelloWorldClient     - javax.namin
g.NameNotFoundException [Root exception is org.omg.CosNaming.NamingContextPackage.NotFound: IDL:omg.
org/CosNaming/NamingContext/NotFound:1.0]
     [java]     at com.sun.jndi.cosnaming.ExceptionMapper.mapException(ExceptionMapper.java:44)
     [java]     at com.sun.jndi.cosnaming.CNCtx.callResolve(CNCtx.java:453)
     [java]     at com.sun.jndi.cosnaming.CNCtx.lookup(CNCtx.java:492)
     [java]     at com.sun.jndi.cosnaming.CNCtx.lookup(CNCtx.java:470)
     [java]     at javax.naming.InitialContext.lookup(InitialContext.java:351)
     [java]     at net.blueslate.sample.ejb.helloworld.HelloWorldClient.main(HelloWorldClient.java:5
4)
     [java] Caused by: org.omg.CosNaming.NamingContextPackage.NotFound: IDL:omg.org/CosNaming/Naming
Context/NotFound:1.0
     [java]     at org.omg.CosNaming.NamingContextPackage.NotFoundHelper.read(NotFoundHelper.java:72
     [java]     at org.omg.CosNaming._NamingContextExtStub.resolve(_NamingContextExtStub.java:406)
     [java]     at com.sun.jndi.cosnaming.CNCtx.callResolve(CNCtx.java:440)
     [java]     ... 4 moreHere is my ejb-jar.xml:
<?xml version="1.0" encoding="UTF-8"?>
<ejb-jar
     xmlns="http://java.sun.com/xml/ns/j2ee"
     xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
     xsi:schemaLocation="http://java.sun.com/xml/ns/j2ee/ejb-jar_2_1.xsd"
     version="2.1">
     <enterprise-beans>
          <session>
               <ejb-name>HelloWorldEJB</ejb-name>
               <home>net.blueslate.sample.ejb.helloworld.HelloWorldRemoteHome</home>
               <remote>net.blueslate.sample.ejb.helloworld.HelloWorldRemote</remote>
               <local-home>net.blueslate.sample.ejb.helloworld.HelloWorldLocalHome</local-home>
               <local>net.blueslate.sample.ejb.helloworld.HelloWorldLocal</local>
               <ejb-class>net.blueslate.sample.ejb.helloworld.impl.HelloWorldImpl</ejb-class>
               <session-type>Stateless</session-type>
               <transaction-type>Container</transaction-type>
          </session>
     </enterprise-beans>
</ejb-jar>Here is my sun-ejb-jar.xml:
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE sun-ejb-jar PUBLIC "-//Sun Microsystems, Inc.//DTD Application Server 9.0 EJB 3.0//EN" "http://www.sun.com/software/appserver/dtds/sun-ejb-jar_3_0-0.dtd">
<sun-ejb-jar>
     <enterprise-beans>
          <ejb>
               <ejb-name>HelloWorldEJB</ejb-name>
               <jndi-name>HelloWorldEJB</jndi-name>
          </ejb>
     </enterprise-beans>     
</sun-ejb-jar>I believe the root cause is that my EJB is not bound to a name within the app server. If I browse the "JNDI tree" from the app server admin console, I can see there is a root element "ejb," but there is nothing underneath. I guess I just expected to find the name of my EJB, "HelloWorldEJB." I swear I could have read somewhere in the documentation for the app server that when you deploy an EJB, the name of the EJB as specified by the "<ejb-name>" element of the ejb-jar.xml deployment descriptor gets automatically bound within the naming server to its home object.
At this point I would appreciate any insight anyone might have regarding this problem. I suspect there is something extra I need to do when deploying my EJB so that its name gets binded to its home object; I just don't have a clue at this point what that is.
I should also mention that I have played with the parameter passed to 'context.lookup()' - I tried passing: "ejb/HelloWorldEJB", "HelloWorldEJB", etc - nothing seems to work. FWIW, if I just pass in "ejb", I don't receive an exception (I was glad to see this work since the JNDI tree-view from the app server admin console shows "ejb" as one of the root-elements within the naming-tree - this indicated to me I was on the right track in my diagnosis of the problem; i.e., it's probably not a connectivity or protocol issue)
Thank you very much for your time and help.

Answer 1

Nevermind folks - I got it to work. All my configuration was correct; I had other issues with the ejb-jar file that the verifier informed me of (my previous deployments were with the verifier turned-off).