1) Setting up the Context properties, which including pointing to the server hosting the JNDI service. This code which you posted, is an example for this:
2) The second part (after the context has been setup) is to do a lookup using a key (also known as JNDI name) which is done as follows:
The com.bekijkhet.HelloStateless is the JNDI name. Even though it looks like a fully qualified classname of the bean interface, in reality it can be any string which represents the JNDI name of the bean. While deploying a bean on the server, each bean has a unique JNDI name on the server, so that the clients can lookup it up using that name.
This is really useful : If the stand-alone java client is running on a different host than the server, set the -Dorg.omg.CORBA.ORBInitialHost property when starting the client JVM. E.g.
java -Dorg.omg.CORBA.ORBInitialHost=com.acme.Host1. This property defaults to localhost, so it is not necessary to set it if the java client is running on the same machine as the server.
thank you for your patients.
let me search for setting JNDI for bean.
Doody calls. I would really rather that it didn't. Comfort me wise and sterile tiny ad: