javax.naming. NoInitialContextException:

[Brahim Bakayoko]

 public class client {
public String doStandalone() {


try {
Context jndiContext = getInitialContext();
Object ref = jndiContext.lookup("TestSessionHome");
TestSessionHome home = (TestSessionHome) PortableRemoteObject.narrow(ref, TestSessionHome.class);

TestSession remote = home.create();
remote.test("[e-mail]");
} catch (RemoteException e) {
} catch (NamingException e) { 
StringWriter sw = new StringWriter();
PrintWriter bf = new PrintWriter(sw);
e.printStackTrace(bf);
return "failed! NamingException" + "\n" + sw.toString();
} catch (CreateException e) { }

}

public Context getInitialContext() throws NamingException {
    Properties p = new Properties();
    p.put(Context.INITIAL_CONTEXT_FACTORY, "com.ibm.websphere.naming.WsnInitialContextFactory");
    p.put(Context.PROVIDER_URL,  "iiop://localhost:2809/");
   
    return new InitialContext(p);
  } 

1. All imports are well set
2. IDE = Websphere studio 5
3. output:
(java.lang.String) failed! NamingException
javax.naming.NoInitialContextException: Cannot instantiate class: com.ibm.websphere.naming.WsnInitialContextFactory. Root exception is java.lang.ClassNotFoundException: com.ibm.websphere.naming.WsnInitialContextFactory
at java.net.URLClassLoader.findClass(URLClassLoader.java:240)
Can anyone tell me how to properly set the jndi settings?
Thanks!
Also: everything works fine when the bean is used in a jsp or servlet either directly or through an access bean.
The above code is for a remote client trying to access the bean.
[ November 25, 2003: Message edited by: Brahim Bakayoko (Ivory Coast) ]

[Brahim Bakayoko]

Still need help on this one...

[Kyle Brown]

I really wish I could say "go get my book", which does cover this, but it won't be in bookstores or Amazon for another two weeks yet. Sigh...
Anyway, the major issue is that you can't create an EJB client in a "standard" Java project in WSAD. It has to be done in an Application Client project, which is part of the same EAR as your EJB classes. This will correctly set the classpaths to allow you to get to classes like InitialContext. Then, you have to make sure that you edit the Module dependencies to ensure that your application client project has a reference to your EJB Project. Finally, you have to make sure you run this as a Java application client, and not as a Java application from the Run... menu.
That's the basics. Hopefully this will help.
Kyle

[Brahim Bakayoko]

Thanks.
I'll make sure to pick up your new book.
Creating a client application did not help however.
Running the app within the web context:

 javax.naming.NameNotFoundException: TestSessionHome 
at com.ibm.ws.naming.jndicos.CNContextImpl.doLookup(CNContextImpl.java:1503) 
at com.ibm.ws.naming.jndicos.CNContextImpl.doLookup(CNContextImpl.java:1457) 
at com.ibm.ws.naming.jndicos.CNContextImpl.lookup(CNContextImpl.java:1167) 
at com.ibm.ws.naming.util.WsnInitCtx.lookup(WsnInitCtx.java:132) 
at javax.naming.InitialContext.lookup(InitialContext.java:359) 

Where would I go to check on my COS naming settings?
Also, I don't get the point of having the client app within the same EAR with the EJBs. This is counter-intuitive to the client being deployed independently. I want to use the client remotely using RMI-IIOP.
[ November 29, 2003: Message edited by: Brahim Bakayoko (Ivory Coast) ]

[Brahim Bakayoko]

up..
Still need help...