OmniNames and bind_context

[Gary D. Duzan]

In Message <199712241055.KAA24354@kirkstone.cam-orl.co.uk> ,
   Tristan Richardson <tjr@cam-orl.co.uk> wrote:

=>> So strictly speaking, allowing references to NamingContexts that are
=>> bound with bind to participate in a resolve of a compound name is
=>> non-compliant. I would think it would be easy to fix, though; just
=>> check for ncontext at each step.
=>> 
=>
=>
=>I believe (hope?) omniNames does exhibit the correct behaviour.

   That's the point. As of 2.2.0, it doesn't. And I just tried the version
with the 2.4.0 snapshot, and it is incorrect, too.

% ./nameclt bind_new_context foo context
IOR:00f21f5c0000002049444c3a436f734e616d696e672f4e616d696e67436f6e746578743a312e300000000001000000000000002c000100000000000f3133322e3139372e3131322e32340000270f00000000000c34a1468e882d620e00000004
% ./nameclt bind bar context IOR:00f21f5c0000002049444c3a436f734e616d696e672f4e616d696e67436f6e746578743a312e300000000001000000000000002c000100000000000f3133322e3139372e3131322e32340000270f00000000000c34a1468e882d620e00000004
% ./nameclt list
(foo,context) binding type ncontext
(bar,context) binding type nobject
% ./nameclt list bar context

   The last line should generate an exception (either NotFound or
CannotProceed; not really sure which is better) but does not.

					Gary Duzan
					GTE Laboratories