82
83 /**
84 * A name-to-object association is called a Binding.
85 */
86 struct Binding
87 {
88 Name binding_name; // name
89 BindingType binding_type; // whether name is bound to an object
90 // or a naming context
91 };
92
93 /**
94 * List of Bindings.
95 */
96 typedef sequence <Binding> BindingList;
97
98 /**
99 * The BindingIterator interface allows a client to iterate through
100 * the bindings using the next_one or next_n operations.
101 *
102 * The bindings iterator is obtained by using the <tt>list</tt>
103 * method on the <tt>NamingContext</tt>.
104 * @see org.omg.CosNaming.NamingContext#list
105 */
106 interface BindingIterator
107 {
108 /**
109 * This operation returns the next binding. If there are no more
110 * bindings, false is returned.
111 *
112 * @param b the returned binding
113 */
114 boolean next_one(out Binding b);
115
116 /**
117 * This operation returns at most the requested number of bindings.
118 *
119 * @param how_many the maximum number of bindings to return
120 *
121 * @param bl the returned bindings
122 */
123 boolean next_n(in unsigned long how_many,
395 InvalidName);
396
397 /**
398 * The destroy operation deletes a naming context. If the naming
399 * context contains bindings, the NotEmpty exception is raised.
400 *
401 * @exception org.omg.CosNaming.NamingContextPackage.NotEmpty Indicates that the Naming Context contains bindings.
402 */
403 void destroy()
404 raises(NotEmpty);
405
406 };
407
408
409 /**
410 * <code>NamingContextExt</code> is the extension of <code>NamingContext</code>
411 * which
412 * contains a set of name bindings in which each name is unique and is
413 * part of Interoperable Naming Service.
414 * Different names can be bound to an object in the same or different
415 * contexts at the same time. Using <tt>NamingContextExt</tt>, you can use
416 * URL-based names to bind and resolve.
417 *
418 * See <a href="http://www.omg.org/technology/documents/formal/naming_service.htm">
419 * CORBA COS
420 * Naming Specification.</a>
421 */
422 interface NamingContextExt: NamingContext
423 {
424 /**
425 * StringName is the Stringified Name, Array of Name Components
426 * represented as a String.
427 */
428 typedef string StringName;
429
430 /**
431 * Address is the Host and Port information represented as a String.
432 */
433 typedef string Address;
434
435 /**
|
82
83 /**
84 * A name-to-object association is called a Binding.
85 */
86 struct Binding
87 {
88 Name binding_name; // name
89 BindingType binding_type; // whether name is bound to an object
90 // or a naming context
91 };
92
93 /**
94 * List of Bindings.
95 */
96 typedef sequence <Binding> BindingList;
97
98 /**
99 * The BindingIterator interface allows a client to iterate through
100 * the bindings using the next_one or next_n operations.
101 *
102 * The bindings iterator is obtained by using the <code>list</code>
103 * method on the <code>NamingContext</code>.
104 * @see org.omg.CosNaming.NamingContext#list
105 */
106 interface BindingIterator
107 {
108 /**
109 * This operation returns the next binding. If there are no more
110 * bindings, false is returned.
111 *
112 * @param b the returned binding
113 */
114 boolean next_one(out Binding b);
115
116 /**
117 * This operation returns at most the requested number of bindings.
118 *
119 * @param how_many the maximum number of bindings to return
120 *
121 * @param bl the returned bindings
122 */
123 boolean next_n(in unsigned long how_many,
395 InvalidName);
396
397 /**
398 * The destroy operation deletes a naming context. If the naming
399 * context contains bindings, the NotEmpty exception is raised.
400 *
401 * @exception org.omg.CosNaming.NamingContextPackage.NotEmpty Indicates that the Naming Context contains bindings.
402 */
403 void destroy()
404 raises(NotEmpty);
405
406 };
407
408
409 /**
410 * <code>NamingContextExt</code> is the extension of <code>NamingContext</code>
411 * which
412 * contains a set of name bindings in which each name is unique and is
413 * part of Interoperable Naming Service.
414 * Different names can be bound to an object in the same or different
415 * contexts at the same time. Using <code>NamingContextExt</code>, you can use
416 * URL-based names to bind and resolve.
417 *
418 * See <a href="http://www.omg.org/technology/documents/formal/naming_service.htm">
419 * CORBA COS
420 * Naming Specification.</a>
421 */
422 interface NamingContextExt: NamingContext
423 {
424 /**
425 * StringName is the Stringified Name, Array of Name Components
426 * represented as a String.
427 */
428 typedef string StringName;
429
430 /**
431 * Address is the Host and Port information represented as a String.
432 */
433 typedef string Address;
434
435 /**
|