[omniORB] corbaloc/corbaname

Richard Hardgrave richard.hardgrave@teradyne.com
Wed, 6 Feb 2002 16:03:57 -0600 (CST)


I guess I'm still a bit foggy on exactly how to
use the corbaloc/corbaname URIs.
First off, I'm using omniORB 3.0.3, on Solaris 2.5.1.

Perhaps the omniORB Guide documentation is throwing
me off.  I can run eg2_impl on one machine (poe) on
our network, and invoke eg2_clt on another machine
(johndeere) with the big, hairy, IOR string for an
argument, and it finds the servant with no problem.

But, if I try using the other URI syntax, the closest
I can get is:

(from johndeere)

# ./eg2_clt 'corbaname::poe.ttd.teradyne.com/NameService#test.my_context/Echo.Object' crap
Caught system exception COMM_FAILURE -- unable to contact the object.

Perhaps I'm just confused about when it is appropriate to
use this format.  Is this format only correct for reaching
a servant, like the Naming Service, that listens on a port #?
The omniORB guide documentation gives reference to the
echo.object - 

      corbaname::myhost/NameService#project/example/echo.obj
      corbaname:rir:/NameService#project/example/echo.obj

But, none of the echo servant examples listen on a port #.
Perhaps I have the Object Key syntax incorrect.  Is there
any other documentation on how to use this syntax?

Thanks,

Richard