[omniORB] Problem connecting naming service

[Klaus Dieter Welast]

"Duncan Grisby" <duncan at grisby.org> wrote:
> On Thursday 5 October, "K.D.Welast at t-online.de" wrote:
> 
> [...]
> > I have done the test with 4.1.0 RC 1 and the problem is still there. 
> > The version 4.1.0 RC 1 binaries are building with VC 7 SP1 on WinXP SP2
> > 
> > Below the trace with -ORBtraceLevel 40 -ORBtraceInvocations 1 for the
> > versions 4.10 RC1 and 4.07
> 
> OK, now I've looked at it closer, it's not the issue I thought it was at
> all. The problem is actually that Visibroker is returning a strange IOR
> in the location forward. Extracting it from the trace, and dumping it
> with catior, it looks like this:
> 
> [.....]
> 
>   The following rules augment the preceding discussion:
> 
>   1. Profiles must be independent, complete, and self-contained. Their
>      use shall not depend on information contained in another profile.
> 
>   2. Any invocation uses information from exactly one profile.
>   
>   ...
> 
> So based on point 2, I think omniORB is right to only use the details in
> the first IIOP profile, and ignore the second one. It wouldn't be hard
> to extend omniORB to use all the IIOP profiles when picking the
> endpoints to try, but I think the spec says it's wrong to do that.
> 
> Cheers,
> 
> Duncan.
> 
> -- 
>  -- Duncan Grisby         --
>   -- duncan at grisby.org     --
>    -- http://www.grisby.org --
> 

Hallo Duncan,

thank you for your investigation and explanation. 
I will try to get some answers from Borland.

Best regards
Mit freundlichen Grüßen
Kl. D. Welast

Hellersberstr. 35A
41460 Neuss
Tel: +49 2131 166657
Mobil: +49 171 5638203
Email: k.d.welast at t-online.de