Issue 2636:  Binding type "n_context":                                                                                                                                                                              (naming_ftf)
Source:  (, )
Nature:  Uncategorized Issue
Severity: 
Summary: Summary: by using bind_context/rebind_context/bind_new_context versus those
 that are bound by using other means?
 
 If an application uses resolve() to lookup a naming context, it has no
 way of telling whether the naming context has the binding type
 n_context. In fact, it doesn"t care.  So an application choosing to do
 piecewise resolution against CosNaming would see a different behavior
 than if it were to do whole resolution. This seems to contradict the
 subsection "Resolution of Compound Names" in Section 4.2, page 4-8. It
 seems that n_context is an implementation issue of CosNaming that is
 exposed to the application.
 
 The suggestion is to remove the third paragraph of the Usage section,
 or to change it so that n_context be set for any naming context bound
 in the namespace.
 
 

Resolution: Clarify role of when naming_contexts participate in name resolution, make text consistent with Usage
Revised Text: Added Note to "Resolution of Compound Names"  at the end of Section 4.2  (3.2) stating that intermediate
name components must be contexts that were bound with bind or rebind_context if they are to take part in name resolution.
Actions taken:
May 5, 1999: received issue
May 4, 2000: closed issue
Discussion: 

End of Annotations:=====
Sender: pwalker@eng.sun.com
Date: Wed, 05 May 1999 13:27:26 -0700
From: Peter Walker <pwalker@eng.sun.com>
Organization: Sun Microsystems
X-Accept-Language: en
To: issues@omg.org
Subject: Interoperable Naming Issues (2 issues)


---------------------------------------------------------------------
Issue: Binding type 'n_context':

Page 4-12: Section 4.3.3 Binding Objects

Why is there a distinction made between naming contexts that are bound
by using bind_context/rebind_context/bind_new_context versus those
that are bound by using other means?

If an application uses resolve() to lookup a naming context, it has no
way of telling whether the naming context has the binding type
n_context. In fact, it doesn't care.  So an application choosing to do
piecewise resolution against CosNaming would see a different behavior
than if it were to do whole resolution. This seems to contradict the
subsection 'Resolution of Compound Names' in Section 4.2, page 4-8. It
seems that n_context is an implementation issue of CosNaming that is
exposed to the application.

The suggestion is to remove the third paragraph of the Usage section,
or to change it so that n_context be set for any naming context bound
in the namespace.





-- 
Peter J. Walker, Sun Microsystems Inc., Java Software, Cupertino, CA.
Tel : (408) 517-5679 (internal 65679)            FAX : (408) 863-3195