[omniORB] Using omniORB's 3.0.1 naming service with Visibroke r 3.3

[Brenneis, Steve]

For some strange reason, VisiBroker wants you to use their proprietary,
non-portable static _bind method on the NamingContext interface to obtain a
root NamingContext. Obviously, this won't work when trying to resolve an
omniNames server because Visi's SmartAgent doesn't know anything about the
omniORB server. You might be able to get Visi to go the
resolve_initial_references route by giving it the omniORB Naming Service
host and port via the ORB initialization parameters. I can't guarantee
whether it will work, I haven't tried it before. Once you get the root
NamingContext, everything should proceed as expected.

Hope this helps.

Steve Brenneis

> -----Original Message-----
> From: Rito Guia [mailto:rguia1@txu.com]
> Sent: Monday, October 23, 2000 4:08 PM
> To: omniorb-list@uk.research.att.com
> Subject: [omniORB] Using omniORB's 3.0.1 naming service with 
> Visibroker
> 3.3
> 
> 
> 
> 
> Hi All,
> 
> Can anybody provide me with any helpful hints and/or 
> suggestions on how I can
> get  a Visibroker 3.3 client program to communicate through 
> omniNames 3.0.1 to
> an omniORB server program.  The server object is located on a 
> different server
> than omniNames and the client program is ran from my desktop. 
>  Anything would be
> helpful.  Thank you.
> 
> RGIII
> 
> 
>