[omniORB] NameService compatibility

[Duncan Grisby]

On Wednesday 28 February, Bert Thomas wrote:

> Is it possible to use the nameservice of omniORB3 with omniORB2.8.0
> clients? I tried this, but the client complains about "ORB
> initialisation problem". "Invalid object reference supplied for
> NAMESERVICE". I copied & pasted the IOR from the output of the
> nameservice into the registry. Whatever I try, it keeps saying this. I
> also tried the corbaloc syntax, that didn't help either. 

omniORB 2.8.0 has a silly bug which prevents it from using omniORB 3's
naming service as an object returned by resolve_initial_references.
You can fix it by updating omniORB 2.8.0 from the bugfixes patch at

  http://www.uk.research.att.com/omniORB/bug280.html

The problem is that 2.8.0 refuses to accept a NameService reference
with a repository id other than IDL:omg.org/CosNaming/NamingContext.
omniORB 3's naming service uses NamingContextExt. An alternative to
fixing 2.8.0 is to cook up a new IOR with the same host, port and
object key, but the expected repoid.

Something like:

$ catior IOR:........
Type ID: "IDL:omg.org/CosNaming/NamingContextExt:1.0"
Profiles:
1. IIOP 1.0 myhost 2809 "NameService"

$ genior IDL:omg.org/CosNaming/NamingContext:1.0 myhost 2809 NameService

IOR:010000002800000049444c3a6f6d672e6f72672f436f734e616d696e672f4e616d6
96e67436f6e746578743a312e300001000000000000002300000001010000070000006d
79686f73740000f90a00000b0000004e616d6553657276696365

Cheers,

Duncan.

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