[omniORB] Registering an Object with more than one NameService???

[Gary D. Duzan]

   No, but you can do it manually using nameclt, and since OmniNames
doesn't change context IORs, you only have to do it once, and it
wouldn't be hard to automate for your own naming scheme.

					Gary Duzan
					Verizon Laboratories



In Message <8625697C.006C47D6.00@smtp2.mcld.net> ,
   "Michael J. Donahue" <mdonahue@McLeodUSA.com> wrote:

=>
=>
=>
=>But does this propagate the IORs of one Name Service to another?
=>
=>- Mike
=>
=>
=>
=>
=>
=>Bruce Visscher <visschb@rjrt.com> on 10/18/2000 01:05:34 PM
=>
=>To:   Michael J. Donahue/MCLEOD@MCLEOD, omniORB mailing list
=>      <omniorb-list@uk.research.att.com>
=>cc:
=>Subject:  Re: [omniORB] Registering an Object with more than one NameService???
=>
=>
=>
=>Michael,
=>
=>"Michael J. Donahue" wrote:
=>> [...]
=>> My ultimate goal is to have a Federated Name Service, but omniORB does not
=>> appear to support this,
=>
=>What ever gave you that idea?
=>
=>Try this:
=>
=>Startup omniNames on two different host/port combinations.  Then bind
=>the IOR of one omniNames server as a context in the other.  Works for
=>me.
=>
=>HTH,
=>
=>Bruce
=>--
=>
=>Bruce Visscher                                        visschb@rjrt.com
=>
=>
=>
=>
=>
=>