[omniORB] RE: using omniNames from java clients

[Heley, Mike]

Thanks Alex.

Using "omniNames -ORBsupportBootstrapAgent 1"  does indeed fix it. I've
switched it on in the config file now.
I guess I should have looked in there first, as the comments are quite
clear. It does seem pretty poor that the Sun Java orb is using an obsolete
protocol, but presumably it will be fixed in their 5.0 release... 

regards,
Mike.

> Date: Wed, 25 Aug 2004 11:12:18 +0100
> From: Alex Tingle <alex.omniorb at firetree.net>
> 
> Mike,
> 
> Try starting omniNames like this:
> 
>   omniNames -ORBsupportBootstrapAgent 1 
> 
> Or you could switch to a better Java ORB.
> 
> -Alex Tingle
> 
> --
> On Wed, 25 Aug 2004 10:43:21 +0100
> "Heley, Mike" <mike.heley at mbda.co.uk> wrote:
> 
> > 
> > I am writing a java client to integrate into an omniorb system and I
> > am puzzled by the following behaviour.
> >  
> > Using the built in orb in J2SE 1.4, if I use the args -ORBInitialHost
> > <host>-ORBInitialPort 2809, the client connects to omniNames but
> > throws an OBJECT_NOT_FOUND on calling resolve_initial_references. I
> > can get it to work using -ORBInitRef
> > NameService=corbaloc::<host>:2809.
> >  
> > That is with the omniNames from V4.0.3 on Solaris, but with omniNames
> > from V3.0.5 on HPUX, the -ORBInitialHost/-ORBInitialPort works okay.
>>  
> > Can anyone explain what's going on?
> >  
> > Thanks,
> > Mike

********************************************************************
This email and any attachments are confidential to the intended
recipient and may also be privileged. If you are not the intended
recipient please delete it from your system and notify the sender.
You should not copy it or use it for any purpose nor disclose or
distribute its contents to any other person.
********************************************************************