[omniORB] Interoperability issue with ORBacus Names / omniORB resolve_initi al_references

[Duncan Grisby]

On Wednesday 4 July, "Hayes, Ted (London)" wrote:

> I am running Orbacus 4.0.5 C++ nameserv on a Solaris 2.6 machine.  On the
> client side I have Windows NT 4 and omniORB 3.0.2 - Similar behaviour occurs
> under both C++ and Python clients, but obviously it's easier to demonstrate
> using Python.  I am using omniORBpy version 1.2.  Normal Python setup..

[...]
> method 1:
>   ns = ORB.resolve_initial_references("NameService")
> 
> method 2:
>   ns = ORB.string_to_object("corbaloc:rir:/NameService")

Both of these use the "administratively configured" naming service.
Have you put the right entries in the registry/configuration file or
used -ORBInitRef on the command line?

Perhaps you are using the old ORBInitialHost, ORBInitialPort
configuration?  That only works with omniNames and the JDK ORB's
naming service.

> method 3:
>   obj = ORB.string_to_object("corbaloc:iiop:mysolarishost:2000/NameService")

This one doesn't rely on any configuration, which is why I suspect
your configuration might be wrong.

>   ns =  obj._narrow(CosNaming.NamingContext)

Note that all three schemes require the narrowing step.

Cheers,

Duncan.

-- 
 -- Duncan Grisby  \  Research Engineer  --
  -- AT&T Laboratories Cambridge          --
   -- http://www.uk.research.att.com/~dpg1 --